Open bellondr opened 1 year ago
Hi @bellondr
This issue doesn't seem to be linked to the datadog
chart, but more linked to the cluster-agent
component that is part of the https://github.com/datadog/datadog-agent repository.
It would be better that you reopen the issue on the https://github.com/datadog/datadog-agent repository and try to contact our support with a cluster-agent flare
@clamoriniere Thanks for your reply Maybe it it cluster-agent issue. But If we set the env in deployment.yaml. we can fix it. So maybe helm chart need to expose these two env in values.yaml
Hello @bellondr
Sorry if I didn't understood your initial message.
DatadogMetric
status? Hi, I'm facing the same issue. @bellondr were you able to fix it?
@njay4928 Sorry to reply too late set
- name: DD_EXTERNAL_METRICS_PROVIDER_MAX_AGE
value: "900"
- name: DD_EXTERNAL_METRICS_PROVIDER_BUCKET_SIZE
value: "900"
in deployment datadog-cluster-agent env
Describe what happened: In aws eks env, when we use datadog metrics in hpa, we found error:
cmd:
kubectl describe HorizontalPodAutoscaler car-service
Warning FailedGetExternalMetric 4m31s (x10889 over 2d5h) horizontal-pod-autoscaler unable to get external metric car-service/datadogmetric@car-service:network-requests/nil: unable to fetch metrics from external metrics API: Internal error occurred: DatadogMetric is invalid, err: Invalid metric (from backend), query: sum:aws.applicationelb.request_count_per_target{service:car-service,stage:stage}.as_count().rollup(sum, 60)
And in cluster agent we found error log:
022-11-17 06:34:37 UTC | CLUSTER | ERROR | (pkg/clusteragent/externalmetrics/provider.go:106 in GetExternalMetric) | ExternalMetric query failed with error: DatadogMetric is invalid, err: Invalid metric (from backend), query: sum:aws.applicationelb.request_count_per_target{service:car-service,stage:stage}.as_count().rollup(sum, 60)
in datadog metrics: kubectl describe datadogmetric network-requests
But the hpa works.
Describe what you expected: There is no error log, and datadogmetric status is right
Steps to reproduce the issue:
Additional environment details (Operating System, Cloud provider, etc):