SLO objective unique identifier
Every SLO objective you create with Nobl9 features a name
identifier in the YAML definition.
When you create a new SLO without specifying the name
,
Nobl9 generates it automatically as you're entering the display name for this objective.
You can then update the name
only through sloctl
.
Such a modification is allowed only once per objective using sloctl
, the Nobl9 Terraform Provider, or the Nobl9 SDK for Go!.
To edit the objective's name
, you can do the following:
- sloctl
- Nobl9 Terraform Provider
- Run
sloctl get slos
and replace the files in your repository with those returned by the command, or - Run
sloctl get slos
, change the generated names, and then runapply
(optional).
For an SLO created in the Nobl9 Terraform Provider with auto-generated names
(like in the example below):
resource "nobl9_slo" "example-slo" {
name = "example-slo"
project = "example-project"
service = "example-service
budgeting_method = "Occurrences"
indicator {
...
}
objective {
name = "objective-1"
value = 2
target = 0.99
count_metrics {
...
}
}
time_window {
...
}
}
You can explicitly rename the objective by modifying the name
fields, as shown below:
resource "nobl9_slo" "example-slo" {
name = "example-slo"
project = "example-project"
service = "example-service
budgeting_method = "Occurrences"
indicator {
...
}
objective {
name = "objective-1"
value = 2
target = 0.99
count_metrics {
...
}
}
time_window {
...
}
}
You canβt change the name
once youβve updated it.
Changing auto-generated objective names won't reset error budget calculations and charts.
Nobl9 requires the name
value to be unique across all objectives within a single SLO.
Also, the objective name
is required in YAML files.
Once you save the objective, name
becomes read-only.