GrafanaNet route: periodically post schemas #458
Merged
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
Dieterbe
force-pushed
the
post-schemas-grafanacloud
branch
2 times, most recently
from
cafd23e
to
7bb2164
Compare
On the grafana cloud side, we want to know the schemas that get applied to metrics. So we periodically post the "parsed" version of it to /metrics/schemas which makes sure to exclude things like comments.
Dieterbe
force-pushed
the
post-schemas-grafanacloud
branch
from
7bb2164
to
12ea3d9
Compare
Dieterbe
commented
Apr 28, 2021
| [hello] | ||
| pattern = .* | ||
| retentions = 10m:90d,10m:365y | ||
| priority = 4294967294 |
There was a problem hiding this comment.
these generated priorities are a bit clunky looking but they work
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.
On the grafana cloud side, we want to know the schemas that get applied
to metrics. So we periodically post the "parsed" version of it to /metrics/schemas
which makes sure to exclude things like comments.
with an unpatched gw, we get 404 back and we handle it gracefully, retrying next time.
with a patched gw that reads the body and returns 200, it can see the schemas as expected