docs: removed macros that do not work in alerting #259
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
gabor
requested review from
yesoreyeram,
zoltanbedi and
gwdawson
and removed request for
a team
zoltanbedi
approved these changes
May 14, 2024
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.
our current documentation claims tha the macros
$__fromand$__toworks with bigquery.this is only true in the dashboard&explore, where these are interpolated by generic grafana javascript code.
these do not work in alerting. this confuses our users who try to use this in alerting.
i decided to simply remove them from the documentation for now.
we may decide to implement them in the backend code later, but that's a separate topic.