aws / aws/containers-roadmap

EKS [Request]: Unable to collect the coredns metrics in datadog

Open
#819 4 comments 4 reactions 0 assignees View on GitHub
EKS
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

Hello,

We have coredns configured as a default eks-componemt for us using the **kube-dns** service in **kube-system** namespace . We are facing issues while. trying to integrate `coredns` with `Datadog` to collect the Coredns Metrics.

It seems we don’t have the metric port **9153** at the `kube-dns` at service level , which is present for the `coredns` pod for which it is not able to fetch the metrics and /metrics is not exposed at the service level to enable the prometheus plugin as per the docs:

https://www.datadoghq.com/blog/monitor-coredns-with-datadog/

https://github.com/DataDog/integrations-core/blob/master/coredns/datadog_checks/coredns/data/auto_conf.yaml

Please let me know , if we have a fix in this situation , do we need to upgrade our EKS version or do a manual patch to include the port configuration at service level.

**Current EKS version: 1.14 and Platform version: eks.8**

Regards,
Uday

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the kube-dns Service in the kube-system namespace and the CoreDNS pod configuration for metrics port 9153. Compare the EKS 1.14 behavior with the linked Datadog CoreDNS integration documentation and auto_conf.yaml. Done means determining whether the service requires a port configuration or an EKS upgrade and documenting the supported fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.