You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently working on a project where monitoring is switching from a legacy system to a Prometheus-based monitoring. The new monitoring will use script_exporter to execute local scripts, created by the application owners.
As most of these scripts are Nagios-plugin style scripts, we need to rewrite all of these scripts to change the output.
What if script_exporter could automatically translate the output to a Prometheus format?
Idea: Add a parameter to enable nagios output translation
HELP anagiosplugin_exit Exit code of anagiosplugin. 0=OK, 1=Warning, 2=Critical
TYPE anagiosplugin_exit gauge
anagiosplugin_exit 2
We can come up and work together with more details, ideas etc. But this issue is mainly to ask you the question: Can something like this be considered from your side? Or do you say from the beginning, nope, won't do?
The text was updated successfully, but these errors were encountered:
Cool! thanks for being open to that suggestion.
It would be more about including the performance output of the Nagios plugins, potentially also some output translation.
A typical output from a Nagios plugin (here check_smart as an example) looks like this:
The exit code of this Nagios plugin is 1 (as the output shows WARNING).
The plugin's (informational) output can be found in the first part before the pipe character |.
Performance data is always behind the pipe character |.
The output for this plugin can be ignored, but there might be other plugins where an output translator could also be helpful.
The idea behind this feature request is to (more or less) support already existing Nagios plugins on systems, which otherwise would require a rewrite to output in Prometheus style. At least for the exit code and for the performance data (= metrics) this should be doable I believe.
PS I'll be at the Open Source Monitoring Conference in Nuremberg next week. If by chance you're there, too, we can discuss about this. :-)
I'm currently working on a project where monitoring is switching from a legacy system to a Prometheus-based monitoring. The new monitoring will use script_exporter to execute local scripts, created by the application owners.
As most of these scripts are Nagios-plugin style scripts, we need to rewrite all of these scripts to change the output.
What if script_exporter could automatically translate the output to a Prometheus format?
Idea: Add a parameter to enable nagios output translation
Not sure yet how the output could look like, e.g.
We can come up and work together with more details, ideas etc. But this issue is mainly to ask you the question: Can something like this be considered from your side? Or do you say from the beginning, nope, won't do?
The text was updated successfully, but these errors were encountered: