SLO creator agent
Summarize
Summary of SLO creator agent
The SLO creator agent in ServiceNow automatically generates service level objectives (SLOs) for services and configuration items (CIs) by analyzing operational data such as incidents, alerts, and outages. This agent supports faster adoption of SLOs and enhances monitoring of service performance within Service Reliability Management (SRM).
Show less
To use the SLO creator agent, you must have Now Assist for ITOM and SRM. The agent runs every 14 days and processes up to 25 services or CIs that do not already have auto-generated SLOs.
Key Features
- Automated SLO Generation: Creates one SLO per service or CI, each containing up to 10 service level indicators (SLIs) based on historical operational data.
- Scope and Scheduling: Runs biweekly, targeting services and CIs without existing auto-generated SLOs.
- Comprehensive Analysis: Evaluates related CIs to identify recurring reliability issues for more accurate SLO creation.
- Active SLOs and Notifications: Generated SLOs are active by default. Teams receive email alerts when the error budget falls to 25% or below, and managers are notified when new SLOs are created.
- Management and Customization: Teams can review, edit, or disable SLOs post-creation. The agent itself can be managed—turned on/off and notification settings adjusted via AI Agent Studio.
- Access and Modification: The agent is accessible in AI Agent Studio under the AI agents tab. Customers can duplicate and modify the agent’s settings, ensuring all related instructions are updated accordingly.
- Default Status: The SLO creator agent is enabled by default within ServiceNow environments utilizing SRM.
Practical Benefits for ServiceNow Customers
- Accelerates the adoption of SLOs by automating their creation, reducing manual effort.
- Improves reliability monitoring through data-driven SLOs that reflect actual service performance.
- Ensures timely notifications to teams and managers, enabling proactive management of service reliability and error budgets.
- Provides flexibility to customize and control SLO definitions and agent behavior to fit organizational needs.
Use the service level objective (SLO) creator agent to auto-generate SLOs for services and configuration items (CIs). The agent can help teams adopt SLOs faster and monitor service performance.
SLO creator agent overview
- Schedule and scope: The SLO creator agent runs every 14 days and processes up to 25 services or CIs. It only processes items without auto-generated SLOs in any state.
- Evaluation process: To generate SLOs, the agent analyzes historical alerts, incidents, and outages associated with a service or CI. If the service or CI has related CIs, the agent also evaluates data from those items to identify recurring reliability issues and create SLOs.
- Results: The agent creates 1 SLO per service or CI with up to 10 service level indicators (SLIs). The generated SLOs are active by default, and the team assigned to the service or CI gets an email when
the error budget falls to 25% or below.
To keep teams informed, email notifications are sent to the relevant team manager when the agent generates new SLOs. SRM managers and responders can review, edit, and turn off the SLOs once they're created.
You can manage the SLO creator agent, including turning the agent on or off and managing notification settings. For more information, see Manage SLO creator agent settings. To view SLOs generated by the agent and review details about their creation, see View AI-generated SLOs.
SLO creator agent
Get auto-generated SLOs to help your teams adopt SLOs and monitor service performance in SRM.
To access the agent in AI Agent Studio:
- Navigate to .
- Select the AI agents tab.
- Select SLO Creator Agent.
The SLO Creator Agent page lets you manage the agent, including defining security controls. To modify the agent, duplicate it and adjust the settings.
AI agent used to generate SLOs
One agent is used to create SLOs in SRM.
| AI agent | AI agent role |
|---|---|
| SLO creator agent | Creates SLOs for SRM services and CIs by examining historical incidents, outages, and alerts. |