Debug level logs are generated without setting logging level to debug for elastic-agent.filebeat/metricbeat datasets.

[amolnater-qasource]

Kibana version: 8.6 BC3 kibana cloud environment

Host OS and Browser version: All, All

Build details:

VERSION: 8.6.0 BC3 Kibana cloud environment
BUILD: 58560
COMMIT: d4567dc2eaa4f59503c1822e1f10bf0292b97066
Artifact Link: https://staging.elastic.co/8.6.0-94db6bc6/downloads/beats/elastic-agent/elastic-agent-8.6.0-windows-x86_64.zip

Preconditions:

1. 8.6 BC3 kibana cloud environment should be available.
2. Never set logging level to debug.

Steps to reproduce:

1. Navigate to Fleet tab.
2. Install agents using Agent policy having only System integration.
3. Navigate to agent logs tab.
4. Observe Debug level logs are generated for elastic-agent.filebeat/metricbeat datasets.

elastic-agent.yml:
elastic-agent.zip

Logs:
logs.zip

Screenshot:

Expected Result:
Debug level logs should not be generated without setting logging level to debug for elastic-agent.filebeat/metricbeat datasets.

What's not working fine:

• This issue is also reproducible for Windows, MAC and Linux agents.

[manishgupta-qasource]

Secondary review for this ticket is Done

[cmacknz]

This should be fixed by #1702, which is not in 8.6 yet.

[cmacknz]

I also think this issue existed before 8.6

[cmacknz]

Will be resolved in the next BC or snapshot build.

[jlind23]

@amolnater-qasource would you mind checking this one again please?

[amolnater-qasource]

Hi @jlind23
We have revalidated this issue on latest 8.6 BC6 kibana cloud environment and observed this issue is fixed now.

Observations:

• Debug level logs are not generated without setting logging level to debug for elastic-agent.filebeat/metricbeat datasets.

Validated OS's:

• Windows, Linux and MAC

Build details:
8.6 BC6 kibana cloud environment
BUILD: 58740
COMMIT: f329a77595950244361736dff7208a810299fd69

Screenshots:

Logs:
[Debug]elastic-agent-diagnostics-2022-12-08T09-35-36Z-00.zip

Hence we are closing this issue and marking this issue as QA:Validated.

Thanks

[ghost]

Bug Conversion:

We have updated 01 testcase for this scenario in our fleet test suite at:

• https://elastic.testrail.io/index.php?/cases/view/15282

Thanks!