- You need the "modify/delete events-to-metrics" capability. How you get that role varies depending on your user model:
Keep in mind these concepts when defining SLIs and SLOs.
In the New Relic ecosystem, every service level is linked to another entity, which is any element in your stack that reports data to us, or that generates data that we have access to. The entity that a service level is related to determines where the SLI/SLO results show.
You can define SLIs on any NRDB event that is reported to New Relic, and therefore you can also base SLIs on custom events. Most custom events are not related to a single New Relic entity, but provide higher level business and user experience insights. In this case, you can still relate the SLI to a specific entity or to a workload.
SLIs are defined as the percentage of good responses out of the total number of valid requests. Most often you’ll set up your SLIs by defining the valid and good pieces:
- A valid request is any request that you want to count as meaningful for your SLIs (for example, all transactions related to an endpoint that weren’t initiated by a health check).
- A good response is any response that you consider to provide a good output for the end-user or client service (for example, the service responded in less than 2 seconds, providing a good navigation experience for the end user).
Alternatively, you can define what you consider to be the bad responses instead:
- A bad response is any response that you consider to provide a bad output (for example, the service responded with a server error, causing the client to fail its flow). New Relic will automatically derive the count of good responses as
valid - bad.
Request-based SLOs are based on an SLI defined as the ratio of the number of good requests to the total number of requests. A request-based SLO is met when that ratio meets or exceeds the target for the compliance period.
In this section you’ll find some SLIs that are typically used to measure the performance of services and browser applications.
Transaction events, these SLIs are the most common for request-driven services:
Based on OpenTelemetry spans, these SLIs are the most common for request-driven services:
The following SLIs are based on Google's Browser Core Web Vitals.
You can create SLIs and SLOs from several places on in our UI:
- From the Service levels view on the top menu. You can associate the SLI with any entity across your accounts, including workloads.
- From the Service levels page in any APM Service. The SLI will be associated with that specific APM service. If you use this starting point, New Relic will automatically create the most common service level indicators for this entity type, based on the latest available data.
- From the Service levels tab in any workload. You can associate the SLI with any entity in the workload, or the workload itself.
Follow these steps:
After you've created an SLI, access the UI and click on the ... menu to edit it: