If the System Probe Agent or Security Agent is disabled, inventory agent may be producing noisy logs. about datadog-agent HOT 9 CLOSED

Hi @ghouse13 / @runlevel5 / @mhmdio,

Just as a note, as @dustmop mentioned, the fix will be included in Agent v7.54.x line of releases (next upcoming minor release) so it's expected that you still see these messages with the current releases.

from datadog-agent.

Correct, that message will no longer be output by the automatic config fetcher.

It was being created in the function FullConfig by this line

from datadog-agent.

Thanks for the explanation! 🙏 🙏

from datadog-agent.

You're welcome! Closing this issue now that the PR has merged, please feel free to reopen if you have any other concerns.

from datadog-agent.

Hello @tawAsh1,

Thank you for reporting this issue. We agree that this logging is unnecessary and too frequent, and so have this PR that removes these messages. After being merged this change will be included in release 7.54 of the Agent, which we expect to be available some time later in Q2.

from datadog-agent.

Thank you very much 👍

Just a question about Pull Requests, are the following messages also suppressed?

Make sure the system-probe is running before requesting the runtime configuration, and contact support if you continue having issues.
Make sure the security-agent is running before requesting the runtime configuration, and contact support if you continue having issues.

This message probably assumes that the target agent is not running when the user intentionally tries to fetch the runtime configuration using the command.
It may be inappropriate(confusable?) as a message when invoked by an automatic fetch from an inventory agent, without the user's direct involvement.

from datadog-agent.

Hi Team,

I am also facing the same issue ,how to disable the system-probe logs

2024-03-28 10:36:14 UTC | CORE | INFO | (comp/metadata/inventoryagent/inventoryagentimpl/inventoryagent.go:196 in getCorrectConfig) | could not fetch system-probe process configuration: Could not reach system-probe: Get "http://localhost/config": dial unix /opt/datadog-agent/run/sysprobe.sock: connect: no such file or directory
2024-03-28 10:36:14 UTC | CORE | INFO | (comp/metadata/inventoryagent/inventoryagentimpl/inventoryagent.go:196 in getCorrectConfig) | could not fetch security-agent process configuration: Could not reach security-agent: Get "https://localhost:5010/agent/config": dial tcp 127.0.0.1:5010: connect: connection refused
Make sure the system-probe is running before requesting the runtime configuration and contact support if you continue having issues
Make sure the security-agent is running before requesting the runtime configuration and contact support if you continue having issues

from datadog-agent.

I can confirm I also run into this same warning with v7.53.0

from datadog-agent.

I also confirm the same - datadog agent with ECS fargate

May 06, 2024 at 13:43 (UTC+3:00) | 2024-05-06 10:43:35 UTC \| CORE \| INFO \| (comp/metadata/inventoryagent/inventoryagentimpl/inventoryagent.go:198 in getCorrectConfig) \| could not fetch system-probe process configuration: Could not reach system-probe: Get "http://localhost/config": dial unix /opt/datadog-agent/run/sysprobe.sock: connect: no such file or directory | datadog_agent
May 06, 2024 at 13:43 (UTC+3:00) | Make sure the system-probe is running before requesting the runtime configuration and contact support if you continue having issues | datadog_agent
May 06, 2024 at 13:43 (UTC+3:00) | 2024-05-06 10:43:35 UTC \| CORE \| INFO \| (comp/metadata/inventoryagent/inventoryagentimpl/inventoryagent.go:198 in getCorrectConfig) \| could not fetch security-agent process configuration: Could not reach security-agent: Get "https://localhost:5010/agent/config": dial tcp 127.0.0.1:5010: connect: connection refused | datadog_agent
May 06, 2024 at 13:43 (UTC+3:00) | Make sure the security-agent is running before requesting the runtime configuration and contact support if you continue having issues | datadog_agent

from datadog-agent.