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

Update pkg-descr #4338

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update pkg-descr #4338

wants to merge 1 commit into from

Conversation

simonmcnair
Copy link

add pertinent information.

add pertinent information.
@@ -3,6 +3,9 @@ written in Go with pluggable metric collectors.

WWW: https://github.com/prometheus/node_exporter

***Please note that this needs to be enabled via Services: Prometheus Exporter.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like you want to add a plugin documentation instead? That would be a good place to add this kind of information about how to set it up.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Considering I spent the afternoon trying to figure out how to do this, and the main place I looked was the plugin file I would say that as a starter for 10 this would be a good 0lace to start. Beyond that some documentation would be good, but I think either the plugin or the service description needs changing to be consistent as it isn't immediately obvious that node-exporter relates to a service description of prometheus at all. Just my 2p tho.

@fichtner
Copy link
Member

fichtner commented Nov 4, 2024

The name is from the upstream daemon. The comment is clear and searchable:

PLUGIN_COMMENT= Prometheus exporter for machine metrics

@simonmcnair
Copy link
Author

Fine. The fact that it was obvious to you is beside the point. My case in point https://forum.opnsense.org/index.php?topic=37011.0

Your call.

@fichtner
Copy link
Member

fichtner commented Nov 5, 2024

I'm trying to separate concerns. Adding more boilerplate everywhere only leads to more maintenance and further hit and misses.

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

Successfully merging this pull request may close these issues.

2 participants