Replace Slo
https://api.eu1.coralogix.com/mgmt/openapi/5/slo/slos/v1Updates an existing SLO.
Authorizations
Request
Query Parameters
Whether to silence data validations.
Body
Definition of an SLO
- oneOf
- Option 1
- Option 2
- Option 3
- Option 4
- Option 1
- Option 2
- Option 3
- Option 1
- Option 2
- Option 3
Definition of an APM-based SLI with automatic query generation
oneOfConfiguration for error-based APM SLI
Additional label-based filters to apply to the metrics
Configuration for latency-based APM SLI
oneOfAverage/mean-based latency measurement
Quantile/percentile-based latency measurement
Threshold in milliseconds. Good when latency <= threshold, bad when latency > threshold.
500Time window for latency calculations. Required. Omitting it is rejected.
Possible values: [WINDOW_SLO_WINDOW_UNSPECIFIED, WINDOW_SLO_WINDOW_1_MINUTE, WINDOW_SLO_WINDOW_5_MINUTES]
WINDOW_SLO_WINDOW_5_MINUTESList of service names to monitor. Required. At least one service; an empty list is rejected.
Possible values: >= 1
["my-service","payment-service"]List of labels.
Human-readable display name for the SLO. Required. A missing or empty name is rejected.
Possible values: non-empty
Example Slo NameService, environment, and team ownership configuration for the SLO group and its permutations.
Product type: APM for application performance monitoring SLOs, UNSPECIFIED for manual/custom SLOs
Possible values: [SLO_PRODUCT_TYPE_UNSPECIFIED, SLO_PRODUCT_TYPE_APM]
SLO_PRODUCT_TYPE_APMDefinition of a request-based SLI based on metrics
Slo time frame.
Possible values: [SLO_TIME_FRAME_UNSPECIFIED, SLO_TIME_FRAME_1_DAY, SLO_TIME_FRAME_7_DAYS, SLO_TIME_FRAME_14_DAYS, SLO_TIME_FRAME_21_DAYS, SLO_TIME_FRAME_28_DAYS, SLO_TIME_FRAME_30_DAYS]
Target compliance percentage threshold for the SLO (e.g., 99.9 for three nines).
99.999Definition of a window-based SLI based on metrics
Response
Response after replacing an existing SLO.
- Option 1
- Option 2
- Option 3
- Option 4
- Option 1
- Option 2
- Option 3
- Option 1
- Option 2
- Option 3
The effected slo alert ids.
Definition of an SLO
oneOfDefinition of an APM-based SLI with automatic query generation
oneOfConfiguration for error-based APM SLI
Additional label-based filters to apply to the metrics
Configuration for latency-based APM SLI
oneOfAverage/mean-based latency measurement
Quantile/percentile-based latency measurement
Threshold in milliseconds. Good when latency <= threshold, bad when latency > threshold.
500Time window for latency calculations. Required. Omitting it is rejected.
Possible values: [WINDOW_SLO_WINDOW_UNSPECIFIED, WINDOW_SLO_WINDOW_1_MINUTE, WINDOW_SLO_WINDOW_5_MINUTES]
WINDOW_SLO_WINDOW_5_MINUTESList of service names to monitor. Required. At least one service; an empty list is rejected.
Possible values: >= 1
["my-service","payment-service"]Server copy of apmSli for APM SLOs. Set by the server; sending it instead of apmSli is rejected.
RFC3339 timestamp of when the SLO was created. Set by the server; a value sent by the client is ignored.
Email or identifier of the user who created the SLO. Set by the server; a value sent by the client is ignored.
[email protected]Grouping labels derived by the server from the SLI. A value sent by the client is rejected.
List of labels.
Human-readable display name for the SLO. Required. A missing or empty name is rejected.
Possible values: non-empty
Example Slo NameService, environment, and team ownership configuration for the SLO group and its permutations.
Product type: APM for application performance monitoring SLOs, UNSPECIFIED for manual/custom SLOs
Possible values: [SLO_PRODUCT_TYPE_UNSPECIFIED, SLO_PRODUCT_TYPE_APM]
SLO_PRODUCT_TYPE_APMDefinition of a request-based SLI based on metrics
Revision of the SLO. Set by the server; a value sent by the client is ignored.
Slo time frame.
Possible values: [SLO_TIME_FRAME_UNSPECIFIED, SLO_TIME_FRAME_1_DAY, SLO_TIME_FRAME_7_DAYS, SLO_TIME_FRAME_14_DAYS, SLO_TIME_FRAME_21_DAYS, SLO_TIME_FRAME_28_DAYS, SLO_TIME_FRAME_30_DAYS]
SLO type derived by the server from the SLI. A window-based metric SLI still reads SLO_TYPE_REQUEST. A value sent by the client must match the SLI type; a different value is rejected.
Possible values: [SLO_TYPE_REQUEST, SLO_TYPE_WINDOW]
SLO_TYPE_REQUESTTarget compliance percentage threshold for the SLO (e.g., 99.9 for three nines).
99.999Deprecated: SLO type string. Set by the server from the SLI; a value sent by the client is ignored.
requestTimestamp of the last update. Set by the server; a value sent by the client is ignored.
Definition of a window-based SLI based on metrics