Skip to content

Conversation

jakobdalsgaard
Copy link

Since, in prometheus, it's very tedious to ignore metrics when scraping, and since I usually have metrics that I would like to sample at high frequency, such as boat position and boat attitude -- whilst other data I'd prefer at lower frequency, such as saloon temperature and humidity -- then I've made some changes to the code such that you can specify a list of regular expressions and any SignalK metric that matches any of these will not published on the /prometheus endpoint, but rather a new /prometheus/lf endpoint.

Then, in prometheus, I can specify two scrape configs, one being high frequency and the other being low frequency.

This might not be the right place to solve this, but it was easy for me to do. This might not be the best solution, some might need more separations; but at least this can be a start :-)

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant