added hide field for ElasticSearchTarget and added ExpressionTarget class #483
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.
What does this do?
The hide option lets us create panels where we can hide some of the queries that we have no intention to show. In combination with the added ExpressionTarget we can display only the calculated values.
Why is it a good idea?
It provides the ability to do calculations with multiple results, e.g. calculate service health rate based on all responses and 2xx/3xx responses.
Context
The added json is supported by Grafana, it can be created by hand.
Questions
No questions. Tested with temporary workaround classes in our project and it works. Note: refID can be used as an alias for the ExpressionTarget.
Rebased onto main and added test class as well.