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
@Syndlex can you confirm that you still have metrics being emitted from the collector at ${env:MY_POD_IP}:8888? Does your collector have service.telemetry.metrics.address set?
I updated from 0.116.0 to 0.117.12, and now the job name used to scrape its own configuration is not working anymore.
This is my setup:
I know that the Prometheus Scraper was updated, so I think the problem is there. The job name is always shown as
job="otelcol-contrib"
.Also,
service.name
is now exported in the labels as:otelcol-contrib;internal_service_name
.Does anyone have an idea of what changed?
I tried using just
- job_name: internal_service_name
and also overwriting it withrelabel_configs
, but neither worked.The text was updated successfully, but these errors were encountered: