We also need to ensure that the logs have proper tagging for easier investigation. (In case we want to add more tags besides the ones provided by the alerting framework.)
In this PR @ymao1 included the rule ID and the rule type ID in the tags. This can be verified locally by enabling this config:
Summary
Currently, we use two loggers for observability rules, and in order to enable those, we need to add two configurations. In this ticket, we want to improve this logic by only using the alerting logger to remove additional loggers on our side. (https://github.com/elastic/kibana/blob/main/x-pack/plugins/observability_solution/[…]/server/lib/rules/custom_threshold/custom_threshold_executor.ts)
This is an example of config for loggers for the custom threshold rule:
We also need to ensure that the logs have proper tagging for easier investigation. (In case we want to add more tags besides the ones provided by the alerting framework.) In this PR @ymao1 included the rule ID and the rule type ID in the tags. This can be verified locally by enabling this config: