[add] Prometheus exporter #68
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
since backhaul does not support multi-server it's usually required to have multiple backhaul instances, and overtime, managing and monitoring all those instances gets harder and harder.
the current monitoring solution is not enough for multiple servers and is incompatible with most modern monitoring tools. (as well as eventual timeouts due to how the network speed is calculated)
this PR adds
/metricendpoint for prometheus scraping as well as a basic abstraction for future monitoring modules.together with node exporter it would be real easy to have all backhaul nodes in one dashboard at one glance.
Description
README.mdto include usage examples.Breaking changes
Note
the legacy monitoring system is kept as default, without specifying
metricsparameter in config or an empty array, it will fall back to the legacy metrics system.