content(blog): victoriametrics through the prometheus provider - #60
Merged
Merged
Conversation
This file contains hidden or 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
1 participant
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.
Adds a blog post on reading VictoriaMetrics through the Prometheus provider: what answers, the three paths VictoriaMetrics does not serve, the
topNparameter behind the Tables tab (libredb/libredb-studio#1162), the small differences in what the server sends, and the read-only guarantee. It links to the provider documentation for the full list of caveats.Every claim was checked against
docs/providers/prometheus.mdor measured against a live server; the MetricsQL expressions were run through the provider. No version numbers in the text.Also bumps the site to v1.3.3, so the release that follows deploys it.
bun run build,bun test(219 pass) andbun run lintpass locally.