Add support for publishing custom prometheus data ( not stat driven ) #3310
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Add support for publishing custom prometheus data ( not stat driven ).
Details
Certain data in OpenSIPS relies on internal counters ( ie. ratelimit, dialog profiles, etc ). There is currently no way to export these to prometheus. Also allows for the script writer to push it's own custom/external data to prometheus ( fetched on the spot, without keeping it as internal statistic in OpenSIPS )
Solution
Run custom OpenSIPS route which returns a JSON formatted AVP containing data to be published to prometheus.
Compatibility
Backwards-compatible.
Special Thanks to Voicenter for sponsoring the work.