Technologies/CoreDNS/coredns_forward_max_concurrent_rejects
CoreDNSCoreDNSMetric

coredns_forward_max_concurrent_rejects

[OpenMetrics V1] Counter of the number of queries rejected because the concurrent queries were at maximum.
Dimensions:None
Available on:DatadogDatadog (1)
Interface Metrics (1)
DatadogDatadog
[OpenMetrics V1] Counter of the number of queries rejected because the concurrent queries were at maximum.
Dimensions:None
Sources
coredns.forward_max_concurrent_rejectsgithub.com
Knowledge Base (1 documents, 0 chunks)
documentationBaseline alerts in monitoring and incident management for Amazon EKS in AMS Accelerate - AMS Accelerate User Guide1457 wordsscore: 0.75AWS Managed Services (AMS) Accelerate documentation describing baseline monitoring alerts for Amazon EKS clusters, including specific CoreDNS monitoring alerts and thresholds. The page covers alert conditions, thresholds, and AMS response actions for various Kubernetes and CoreDNS issues including service failures, latency, and errors.
Related Insights (1)
DNS Resolution Latency Spikes Under Concurrent Loadwarning

High concurrent query volume exceeds forward plugin's max_concurrent setting, causing queries to queue and response times to spike, particularly impacting applications with aggressive retry logic.

▸