prometheus / prometheus/node_exporter

supervisord collector failed

Open
#1,794 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
13.8k
Forks
2.7k
Avg merge
1d 23h
Merged PRs (30d)
8

Description

Host operating system: output of uname -a
Linux ip-100-71-24-185 4.15.0-1065-aws #69-Ubuntu SMP Thu Mar 26 02:17:29 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

node_exporter version: output of node_exporter --version

node_exporter, version 0.14.0-rc.2 (branch: master, revision: 0e60bb8e005c638605e59ac3f307e3d47e891a9f)
  build user:       root@504a104b89f5
  build date:       20170307-14:41:31
  go version:       go1.7.5

node_exporter command line flags
./node_exporter -collectors.enabled=supervisord -collector.supervisord.url="http://127.0.0.1:9001"

Are you running node_exporter in Docker?
No

What did you do that produced an error?
Starting the node_exporter with --collector.supervisord enabled, supervisord is listening on 127.0.0.1:9001
but when you try to see supervisord metrics by Curl it gives below output and supervisord collector get failed.

curl http://localhost:9100/metrics |grep "supervisor*"
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  7523  100  7523    0     0  1224k      0 --:--:-- --:--:-- --:--:-- 1224k
node_exporter_scrape_duration_seconds{collector="supervisord",result="error",quantile="0.5"} 1.2884e-05
node_exporter_scrape_duration_seconds{collector="supervisord",result="error",quantile="0.9"} 1.2884e-05
node_exporter_scrape_duration_seconds{collector="supervisord",result="error",quantile="0.99"} 1.2884e-05
node_exporter_scrape_duration_seconds_sum{collector="supervisord",result="error"} 0.0028471110000000003
node_exporter_scrape_duration_seconds_count{collector="supervisord",result="error"} 3

ERRO[0054] ERROR: supervisord collector failed after 0.000016s: connection is shut down source="node_exporter.go:92"

What did you expect to see?
want to see supervisord metrics

What did you see instead?
supervisord collector failed

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure with node_exporter using --collector.supervisord and the reported supervisord URL, then inspect the supervisord collector's connection handling. Done means the collector no longer reports an error and supervisord metrics appear in the /metrics output.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.