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
After integrating it into our Kubernetes environment, we identified an issue with the collected metrics.
Problem
Our Upbound Crossplane environment is highly available, meaning we have multiple upbound_crossplane pods running. Each pod exposes the /metrics endpoint with its metrics.
Datadog collects values from all endpoints of all pods via a discovery process, as we only set the namespace of the pods. These metrics are then divided by kube_node, but since upbound_crossplane runs as a Deployment (not a DaemonSet), multiple pods can run on the same node. This leads to duplicated values in these cases.
Additionally, this approach complicates dashboard usage. Nodes and pods are dynamically created and terminated based on cluster demand. Since kube_node changes throughout the day, we cannot use it as a filter—only as a grouping key. This significantly limits our ability to use these metrics effectively in dashboards and monitors.
Expected Behavior
Ideally, Datadog should collect the /metrics endpoint from only one of the Upbound replicas instead of all of them, avoiding duplicated values.
Suggested Solutions
Implement a way to collect metrics from only one replica of Upbound Crossplane.
Would appreciate any suggestions or guidance on resolving this issue!
Thanks!
The text was updated successfully, but these errors were encountered:
Description
We are using the Upbound UXP integration:
https://github.com/DataDog/integrations-extras/tree/master/upbound_uxp
After integrating it into our Kubernetes environment, we identified an issue with the collected metrics.
Problem
Our Upbound Crossplane environment is highly available, meaning we have multiple upbound_crossplane pods running. Each pod exposes the /metrics endpoint with its metrics.
Datadog collects values from all endpoints of all pods via a discovery process, as we only set the namespace of the pods. These metrics are then divided by kube_node, but since upbound_crossplane runs as a Deployment (not a DaemonSet), multiple pods can run on the same node. This leads to duplicated values in these cases.
Additionally, this approach complicates dashboard usage. Nodes and pods are dynamically created and terminated based on cluster demand. Since kube_node changes throughout the day, we cannot use it as a filter—only as a grouping key. This significantly limits our ability to use these metrics effectively in dashboards and monitors.
Expected Behavior
Ideally, Datadog should collect the /metrics endpoint from only one of the Upbound replicas instead of all of them, avoiding duplicated values.
Suggested Solutions
Would appreciate any suggestions or guidance on resolving this issue!
Thanks!
The text was updated successfully, but these errors were encountered: