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

How to use simple_prometheus receiver #7180

Closed
Tracked by #11504
jinxin-fu opened this issue Jan 17, 2022 · 7 comments
Closed
Tracked by #11504

How to use simple_prometheus receiver #7180

jinxin-fu opened this issue Jan 17, 2022 · 7 comments

Comments

@jinxin-fu
Copy link

jinxin-fu commented Jan 17, 2022

the otel configured as follow:

  prometheus_simple:
    collection_interval: 5s
    # the federation endpoint:
    # Read more about it here: https://prometheus.io/docs/prometheus/latest/federation/
    # You can query the federation with PromQL, encoded as part of the query string.
    endpoint: http://prometheus-kube-prometheus-hypermoni.hypermonitor.svc:9090
    metrics_path: /federate
    params:
      'match[]':
        - '{job="serviceMonitor/hypermonitor/prometheus-kube-prometheus-node-exporter/0"}'
        - '{__name__=~"job:.*"}'

Error: cannot load configuration: unknown receivers type "prometheus_simple" for prometheus_simple
2022/01/17 01:27:33 collector server run finished with error: cannot load configuration: unknown receivers type "prometheus_simple" for prometheus_simple

How to use the receiver in opentelemetry-collector-contrib such as prometheus_simple

@jinxin-fu jinxin-fu added the bug Something isn't working label Jan 17, 2022
@jpkrohling jpkrohling added the comp:prometheus Prometheus related issues label Jan 17, 2022
@gouthamve
Copy link
Member

Hi, what version and docker image for the collector are you using? prometheus_simple exists in otecolcontrib and not the main otel collector. Do you see it when using this image? otel/opentelemetry-collector-contrib:0.42.0

@jinxin-fu
Copy link
Author

jinxin-fu commented Jan 24, 2022

Thanks,I change the image to otel/opentelemetry-collector-contrib:latest and meet the follow error:

2022-01-24T02:29:25.033Z        warn    internal/metricsbuilder.go:125  Failed to scrape Prometheus endpoint    {"kind": "receiver", "name": "prometheus_simple", "scrape_timestamp": 1642991364948, "target_labels": "map[__name__:up instance:prometheus-kube-prometheus-hypermoni:9090 job:prometheus_simple/prometheus-kube-prometheus-hypermoni:9090]"}

@kevinat
Copy link

kevinat commented May 19, 2022

Thanks,I change the image to otel/opentelemetry-collector-contrib:latest and meet the follow error:

2022-01-24T02:29:25.033Z        warn    internal/metricsbuilder.go:125  Failed to scrape Prometheus endpoint    {"kind": "receiver", "name": "prometheus_simple", "scrape_timestamp": 1642991364948, "target_labels": "map[__name__:up instance:prometheus-kube-prometheus-hypermoni:9090 job:prometheus_simple/prometheus-kube-prometheus-hypermoni:9090]"}

+1

Same error with otel/opentelemetry-collector-contrib:0.50.0, and all metrics from this instance failed to be scraped

@codeboten codeboten added the unmaintained Identifies issues/prs for unmaintained components label Jun 23, 2022
@codeboten codeboten added exporter/simpleprometheus and removed comp:prometheus Prometheus related issues labels Jun 24, 2022
@fatsheep9146
Copy link
Contributor

metricsbuilder.go

Can you share your configuration file ? @kevinat

@github-actions
Copy link
Contributor

github-actions bot commented Nov 9, 2022

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label Nov 9, 2022
@atoulme atoulme added waiting for author and removed unmaintained Identifies issues/prs for unmaintained components labels Mar 11, 2023
@github-actions github-actions bot removed the Stale label Apr 18, 2023
@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label Jun 19, 2023
@github-actions
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants