Description
**Agent Environment**
===============
Agent (v7.65.1)
===============
Status date: 2025-05-13 14:36:25.474 UTC (1747146985474)
Agent start: 2025-05-13 12:54:19.295 UTC (1747140859295)
Pid: 135078
Go Version: go1.23.8
Python Version: 3.12.9
Build arch: amd64
Agent flavor: agent
FIPS Mode: not available
Log File: /var/log/datadog/agent.log
Log Level: INFO
Paths
=====
Config File: /etc/datadog-agent/datadog.yaml
conf.d: /etc/datadog-agent/conf.d
checks.d: /etc/datadog-agent/checks.d
=============
Process Agent
=============
Status: Not running or unreachable
=================
Process Component
=================
Enabled Checks: [process rtprocess]
System Probe Process Module Status: Not running
Process Language Detection Enabled: False
=================
Process Endpoints
=================
https://process.datadoghq.com - API Key ending with:
- b5e4f
Describe what happened:
with the change in 7.65.0 to set the process checks to run in the core agent, it appears that datadog.process.processes.host_count is not longer being properly tagged. we see it disappear for hosts that upgraded to that version. however if we set run_in_core_agent: false the metric starts populating again. The different appears to be that the process_agent sends the metric via dogstatsd, which adds appropriate tags, but the core agent looks to be sending the metric directly without adding any tags first.
Describe what you expected:
metric continues to be visible for all hosts.
Steps to reproduce the issue:
upgrade from 7.64.3 or earlier to 7.65.0+ with the default configuration for run_in_core_agent
Additional environment details (Operating System, Cloud provider, etc):
Ubuntu 20.04, 24.04
GCP