Skip to content

[Collector-chart] Self Monitoring not Setting Job name #1562

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Syndlex opened this issue Mar 7, 2025 · 4 comments
Open

[Collector-chart] Self Monitoring not Setting Job name #1562

Syndlex opened this issue Mar 7, 2025 · 4 comments

Comments

@Syndlex
Copy link

Syndlex commented Mar 7, 2025

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:

- job_name: telemetry/internal_service_name
  scrape_interval: 20s
  static_configs:
    - targets:
        - ${env:MY_POD_IP}:8888

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 with relabel_configs, but neither worked.

@TylerHelmuth
Copy link
Member

@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?

@Syndlex
Copy link
Author

Syndlex commented Mar 10, 2025

@TylerHelmuth service.telemetry.metrics.address yes I still get metrics. But the job label is broken.

@TylerHelmuth
Copy link
Member

The chart didn't change anything, maybe this is a bug in the prometheus receiver?

@Syndlex
Copy link
Author

Syndlex commented Mar 11, 2025

yes. I think its this issue: open-telemetry/opentelemetry-collector-contrib#38097

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants