RUM Performance SLO in ObserveOps
ObserveOps (formerly known as AIOps) lets you create Service Level Objectives for RUM applications you already monitor in the RUM module. Use RUM Performance SLOs to measure end-user experience and application performance compliance using RUM metrics and track achievement through the same SLO framework you use for infrastructure.
Prerequisites
Before you create a RUM Performance SLO, confirm the following:
- At least one RUM application is active and sending data to ObserveOps.
- RUM data appears in the RUM module with metrics available.
- You have permissions to create SLO profiles in Settings.
How It Works
ObserveOps evaluates RUM SLOs against counters collected from monitored RUM applications. You define one or more conditions using a counter, an operator, and a threshold value. ObserveOps evaluates each condition at the frequency you set — Daily, Weekly, Monthly, or Quarterly — and calculates an achieved percentage against your target.
When you add multiple conditions, ObserveOps evaluates them using the same multi-condition logic it applies to infrastructure and APM Performance SLOs. This lets you combine metrics like page load time and error rate into a single compliance profile.
Configure a RUM Performance SLO
- Go to Settings from the main menu.
- Select Service Level Objectives, then click SLO Profile.
- Click Create SLO Profile.
- Set SLO Type to Performance.
- Select the RUM tab in the performance SLO configuration area.
- Fill in the RUM condition fields:
| Field | Description |
|---|---|
| Counter | Select a RUM metric — e.g., page load time, error rate, session duration, first contentful paint. |
| Operator | Choose the comparison direction: >, <, >=, <=, or =. |
| Value | Enter the threshold number. Units update automatically based on the selected counter. |
| Source Filter | Filter by a specific dimension of the RUM application or tag. |
| Source | Select the RUM application or RUM tag to evaluate. |
- To add more conditions, click Add Condition and repeat step 6.
- Fill in the remaining SLO fields:
| Field | Description |
|---|---|
| SLO Name | A unique name for this SLO profile. |
| SLO Description | A short explanation of what this SLO measures. |
| Target (%) | The minimum compliance percentage required to meet the SLO. |
| Warning (%) | An early-alert threshold above the target. Must be higher than the target. |
| Frequency | Evaluation window: Daily, Weekly, Monthly, or Quarterly. |
| Start Date | The date ObserveOps begins collecting data. Only future dates are supported. |
| Tags | Custom tags for grouping and filtering SLO profiles. |
| Notify Team | Teams or individuals to notify when the SLO breaches a threshold. |
- Click Create SLO Profile.
Your RUM SLO appears in the SLO Profile list with Status: ON.
You can edit only SLO Description, Tags, and Notify Team after you create the profile.
View RUM SLO Results
RUM SLOs appear in all existing SLO views — Visualization, History, Dashboards, Reports, and Widgets, without extra configuration.
Each RUM SLO card in the Visualization view shows Target, Achieved %, Violation %, and a trend chart. Click any card to open the service drill-down with full compliance details.
Example
Your e-commerce team monitors the checkout application with RUM. You create a RUM Performance SLO targeting page_load_time < 2s and error_rate < 0.5%, with a Weekly frequency and a 98% target. Each Monday, the SLO report shows whether the checkout experience met the weekly target — giving you concrete data for your product reliability review.
Troubleshooting
RUM tab does not appear in the Performance SLO form
Cause: No RUM applications are active, or the RUM module is not licensed. Fix: Verify that at least one RUM application appears in the RUM module with live data. Contact your ObserveOps administrator if RUM is not in your navigation.
SLO shows 0% achieved immediately after creation
Cause: SLO evaluation starts at the beginning of the next evaluation window. Fix: Wait for the first evaluation window to complete.