Skip to content

SLO burnRate rule should indicate user error when SLO itself is not found #230128

@pmuellr

Description

@pmuellr

We've seen versions of this message in our logs:

Executing Rule {{space}}:slo.rules.burnRate:{{rule-id}} has resulted in Error: 
SLO [{{slo-id}}] not found - SLONotFound: SLO [{{slo-id}}] not found
    at KibanaSavedObjectsSLORepository.findById (@kbn/slo-plugin/server/services/slo_repository.js:53:13)
    at Object.executor (@kbn/slo-plugin/server/lib/rules/slo_burn_rate/executor.js:51:15)
    ...

This error is flagged as a framework error, but should be flagged as a user error.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Feature:AlertingFeature:Alerting/RuleTypesIssues related to specific Alerting Rules TypesTeam:ResponseOpsPlatform ResponseOps team (formerly the Cases and Alerting teams)Team:obs-ux-managementObservability Management User Experience TeambugFixes for quality problems that affect the customer experience

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions