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
I am asking to improve the default settings of agent to point to vmsingle-victoria-metrics-k8s-stack.monitoring-system.svc.cluster.local. (with dot on the end) effectively eliminating extra DNS requests. Probably it is the best solution. The only drawback that then we need to put a cluster TLD (cluster.local) as a value in helm chart. But it is ok for many operators (FluxCD, altinity operator and others have the same setting).
The text was updated successfully, but these errors were encountered:
Good day!
The frest installation EKS + latest victoria k8s metrics stack.
In parallel the coroot solution is installed.
I am observing the next
It is the excessive DNS requests from victoria metrics agent to different non-existing domain names in the cluster like:
vmsingle-victoria-metrics-k8s-stack.monitoring-system.svc.svc.cluster.local
vmsingle-victoria-metrics-k8s-stack.monitoring-system.svc.monitoring-system.svc.cluster.local
I am asking to improve the default settings of agent to point to
vmsingle-victoria-metrics-k8s-stack.monitoring-system.svc.cluster.local.
(with dot on the end) effectively eliminating extra DNS requests. Probably it is the best solution. The only drawback that then we need to put a cluster TLD (cluster.local
) as a value in helm chart. But it is ok for many operators (FluxCD, altinity operator and others have the same setting).The text was updated successfully, but these errors were encountered: