-
Notifications
You must be signed in to change notification settings - Fork 486
Prometheus Output #175
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
Prometheus Output #175
Conversation
Closing for now. Until I get my head around Prometheus and how Goss output to it might be useful. |
@pysysops Did you have any luck, wrapping your head around this one? It would be awesome to integrate Goss with Prometheus for automated detection of system changes / continuous infrastructure testing. |
@pysysops I would also really appreciate this feature. |
If somebody needs this, I created a sidecar container, who does the exporting at https://github.com/DracoBlue/goss-metrics-exporter |
Here's an interesting output idea I had...
I've taken a naive approach to get output that matches the text format described here:
https://prometheus.io/docs/instrumenting/exposition_formats/
Here's some example output:
The metric value for each test is the duration of that particular test (r.Duration) which might be useful for graphing.
Most of the useful information is in the metric labels which makes it easy query on the prometheus server.
Currently the metrics are untyped and I'd like to get a Prometheus Server container up and running and get some screenshots to show the value of this output (if any).