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
When configuring our load-balancing collector to target our backend collectors via the k8s resolver, we noticed that while the DNS resolution worked fine and the collectors received evenly distributed traffic, the load-balancer would consistently recycle the endpoints at a set cadence (around every 3 minutes). The endpoints would be unchanged.
We added some log statements to the k8s resolver/handler, and they revealed that the OnUpdate() function in the handler was being invoked. This would imply that some event was triggering the update, but k get endpoints opentelemetry-global-gateway-collector --watch --output-watch-events=true returned no events for several hours when ran manually.
The net result was no actual changes to the service endpoints, but the exporter would consistently dispose and construct new exporters.
Steps to Reproduce
Configure the k8s resolver to point to a service representing
Expected Result
The OnUpdate() call in k8s handler only runs when updates occur in the service endpoints pointed to by the k8s resolver.
Actual Result
OnUpdate() is invoked at a recurring frequency of around every 3 minutes, regardless of changes to the service it points to.
Component(s)
exporter/loadbalancingexporter
What happened?
Description
When configuring our load-balancing collector to target our backend collectors via the k8s resolver, we noticed that while the DNS resolution worked fine and the collectors received evenly distributed traffic, the load-balancer would consistently recycle the endpoints at a set cadence (around every 3 minutes). The endpoints would be unchanged.
We added some log statements to the k8s resolver/handler, and they revealed that the
OnUpdate()
function in the handler was being invoked. This would imply that some event was triggering the update, butk get endpoints opentelemetry-global-gateway-collector --watch --output-watch-events=true
returned no events for several hours when ran manually.The net result was no actual changes to the service endpoints, but the exporter would consistently dispose and construct new exporters.
Steps to Reproduce
Configure the k8s resolver to point to a service representing
Expected Result
The
OnUpdate()
call in k8s handler only runs when updates occur in the service endpoints pointed to by the k8s resolver.Actual Result
OnUpdate()
is invoked at a recurring frequency of around every 3 minutes, regardless of changes to the service it points to.Collector version
v0.105.0
Environment information
Environment
OS: Ubuntu 22.04
Compiler: go1.22.6
OpenTelemetry Collector configuration
Log output
Sample Log Output:
Additional context
No response
The text was updated successfully, but these errors were encountered: