-
Notifications
You must be signed in to change notification settings - Fork 8.6k
[Alerting] Add telemetry for event log information #101809
Copy link
Copy link
Closed
Labels
Feature:AlertingFeature:Alerting/RulesFrameworkIssues related to the Alerting Rules FrameworkIssues related to the Alerting Rules FrameworkFeature:TelemetryTeam:ResponseOpsPlatform ResponseOps team (formerly the Cases and Alerting teams) t//Platform ResponseOps team (formerly the Cases and Alerting teams) t//estimate:smallSmall Estimated Level of EffortSmall Estimated Level of EfforttelemetryIssues related to the addition of telemetry to a featureIssues related to the addition of telemetry to a feature
Metadata
Metadata
Assignees
Labels
Feature:AlertingFeature:Alerting/RulesFrameworkIssues related to the Alerting Rules FrameworkIssues related to the Alerting Rules FrameworkFeature:TelemetryTeam:ResponseOpsPlatform ResponseOps team (formerly the Cases and Alerting teams) t//Platform ResponseOps team (formerly the Cases and Alerting teams) t//estimate:smallSmall Estimated Level of EffortSmall Estimated Level of EfforttelemetryIssues related to the addition of telemetry to a featureIssues related to the addition of telemetry to a feature
Type
Fields
Give feedbackNo fields configured for issues without a type.
Currently alerting telemetry collects information from the
.kibanaindex where thealertsaved objects are stored. Should we consider adding information from the event log to the telemetry data? Now that we are storing rule type id, we could collect information like number of executions that resulted in errors broken down by rule type? Execution durations by rule type? We should consider whether some of this information might be redundant with what's provided in the task manager health endpoint.