Skip to content
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

ability to check Prometheus Receiver scrape target health #2463

Closed
jessegoodier opened this issue Nov 6, 2023 · 4 comments
Closed

ability to check Prometheus Receiver scrape target health #2463

jessegoodier opened this issue Nov 6, 2023 · 4 comments
Labels

Comments

@jessegoodier
Copy link

Describe the question

Is it possible to check the health of the scrape jobs of the Prometheus Receiver when a target is down?
Even with debug logging, I see nothing, just that the job is added.

Steps to reproduce if your question is related to an action

I have:

    exporters:
      logging:
        loglevel: debug

What did you expect to see?

Ideally, jobs with no targets scraping, like you see in the targets page of a prometheus UI.

Environment

my scrape config config:

    receivers:
      prometheus:
        config:
          global:
            scrape_interval: 15s
            scrape_timeout: 10s
          scrape_configs:
          - job_name: kubecost
            honor_labels: true
            # scrape_interval: 1m
            # scrape_timeout: 60s
            metrics_path: /metrics
            scheme: http
            dns_sd_configs:
            - names:
              - adot-primary-cost-analyzer.adot-kubecost-bad
              # ^ intentional mistake
              type: 'A'
              port: 9003
            relabel_configs:
            - source_labels: [__address__]
              target_label: alpha_eksctl_io_cluster_name
              replacement: qa-eks1

If this is documented somewhere, it is difficult to find.

Copy link
Contributor

github-actions bot commented Jan 7, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale label Jan 7, 2024
@jatinmehrotra
Copy link

Even i am looking for something similar
@jessegoodier did you solved this?

Copy link
Contributor

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale label Apr 14, 2024
@jessegoodier
Copy link
Author

I suppose the best method for testing is to install prometheus and use the same scrape config there.

Not hard, just tedious.

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

No branches or pull requests

2 participants