Tyler Helmuth
Tyler Helmuth
I'm not super familiar with the otel-allocator housed in the operator repo. Its goal is to load balance Prometheus endpoints that the collector's Prometheus receiver would scrape? Can it be...
That thread reads to me like the target allocator needs to be managed via the operator. There is an operator chart, that would probably be best place to enable this...
@jaronoff97 sounds good to me, interested to see the results.
The demo helm chart now supports this. I believe this issue can be closed.
@dmitryax please review
@dmitryax please review
@dmitryax still relevant. I am going to do more work after this to address individual service env vars
@povilasv switching to `resource` is better, but a breaking change for existing users. It seems relatively harmless, but could have big implications for users who are relying on those attributes...
> I was thinking on how do we fix it long term, and what do you think if we use copy transformation to set both resource attributes and log attributes?...
@oxeye-schmil The collector chart has .Values.serviceMonitor that when enabled will create a service monitor to scrape the collector's metrics endpoint, and any other endpoints you specify. For prometheusexporter examples checkout...