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

Why deprecate the supervisord collector? #2703

Closed
yangfan-witcher opened this issue May 29, 2023 · 3 comments
Closed

Why deprecate the supervisord collector? #2703

yangfan-witcher opened this issue May 29, 2023 · 3 comments

Comments

@yangfan-witcher
Copy link

Hello developers, I saw it in the update log of the latest v1.6.0 version on May 27:

”[CHANGE] Deprecate supervisord collector #2685

we use this method heavily in our production environment , Please allow me to take the liberty to ask why this is ?

@SuperQ
Copy link
Member

SuperQ commented May 29, 2023

We have decided that process supervisors are out of scope for the node_exporter. They were added at a time when we didn't have a good guidelines and practices. It lead to a number of collector functions that should have been separate exporters.

Supervisors like runit and supervisord fall into that category, because there can be multiple supervisors installed on a given node.

@akuna-yuxiang
Copy link

Do we have any recommended alternatives for the supervisord collector if it's deprecated?

@SuperQ
Copy link
Member

SuperQ commented May 23, 2024

@prometheus prometheus locked as resolved and limited conversation to collaborators May 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants