-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Closed
Labels
Team:actionable-obsFormerly "obs-ux-management", responsible for SLO, o11y alerting, significant events, & synthetics.Formerly "obs-ux-management", responsible for SLO, o11y alerting, significant events, & synthetics.
Description
Summary
Spaces are a Kibana concept, but SLO resources like transforms and ingest pipelines are not space aware. Therefore if a user attempts at creating 2 SLOs with the same ID in 2 different spaces, the second SLO will not be created due to the transforms already existing, but its rollback procedures will remove resources (pipeline) that are used by the first SLO since they share the same internal id...
We have two solutions, either we make every resources space aware, e.g. include the space within the name/id of the resource (pipeline, transform, etc..) but we start reaching the limit of the transform id max length...
Or, we ensure the SLO id is unique across all spaces. I would suggest going with this approach as it requires the less changes.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Team:actionable-obsFormerly "obs-ux-management", responsible for SLO, o11y alerting, significant events, & synthetics.Formerly "obs-ux-management", responsible for SLO, o11y alerting, significant events, & synthetics.