You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Normally metrics are collected for both of those instances (it is a single application), but sometimes after a deployment (application restart) we completely lose metrics for one of those instances; only restart of the datadog agent resolves the issue.
Using different names for the instances does seem to resolve the issue for us.
I suspect this might be because the instances that fail to fetch metrics are stored in a map keyed on instance name so during an application restart one of the instances would overwrite the other.
The text was updated successfully, but these errors were encountered:
We have 2 jmx configurations one in
conf.d/jmx.d/conf.yaml
:and another in
conf.d/kafka.d/conf.yaml
:Normally metrics are collected for both of those instances (it is a single application), but sometimes after a deployment (application restart) we completely lose metrics for one of those instances; only restart of the datadog agent resolves the issue.
Using different names for the instances does seem to resolve the issue for us.
I suspect this might be because the instances that fail to fetch metrics are stored in a map keyed on instance name so during an application restart one of the instances would overwrite the other.
The text was updated successfully, but these errors were encountered: