[APM] POC: Add support for additional dimensions in apm rules #143913
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.
This is a POC and currently only for demo purposes. Review not needed
Early POC (frontend only) for adding additional dimensions to APM rules. This aims to solve usecase 1 and three in the APM Alerting use cases.
By adding a new dimension (eg.
transaction.type
) the dimension will be added as a key to the multi_terms agg.In the case of
transaction.type
, it will be possible to select "All", and be notified when any transaction group has a latency higher than the threshold. It will also be possible to create rules that only monitor a specific transaction group.Note: needs design
We have three rule types in APM that will benefit from this, with the given dimensions:
transaction.name
,container.id
,kubernetes.pod.name
,service.version
transaction.name
,container.id
,kubernetes.pod.name
,service.version
error.grouping_key
,transaction.name
,container.id
,kubernetes.pod.name
,service.version