View generated SLOs

  • Versão de lançamento: Australia
  • Atualizado 12 de mar. de 2026
  • 2 min. de leitura

    • View service level objectives (SLOs) generated by the SLO creator agent and review information about how they were created.

    Antes de Iniciar

    You must have AI Agents for SLO and Service Reliability Management (SRM) installed on your instance. For more information, see Install Now Assist plugins and Install Service Reliability Management from Admin Center or ServiceNow Store.

    For an overview of how and when the SLO creator agent generates SLOs, see Generating service level objectives.

    Role required: srm_manager, srm_responder, or srm_admin

    Procedimento

    1. Navigate to Workspaces > Service Operations Workspace > Services.
    2. Select a service and then select the Reliability Metrics tab.
    3. Select an SLO generated by the SLO creator agent.
      SLOs generated by the agent display Now Assist in the Created by column.
    4. Select the Details tab.
    5. In the Activity panel, review the work notes.
      SLOs generated by the SLO creator agent include work notes that summarize the data analyzed and configuration used during creation. The following example shows the type of information recorded in the work notes:
      === AI-Generated SLO ===

[Issue Pattern Description]
Analysis of 15 alerts over the last month revealed ten distinct reliability-impacting patterns for the Webhook Delivery Tracking Service.
Critical webhook delivery failures, data contract violations, SAML assertion rejections, RBAC permission denied spikes, Kafka consumer lag,
JSON deserialization failures, AZ failover health check failures, schema registry compatibility failures, JWT signature validation failures, 
and gRPC deadline exceeded errors were identified. Each pattern was validated through field-value mapping and encoded query construction, 
ensuring actionable and trackable SLIs.

[Metrics]
• In the last Month: 0 Major Incidents, 0 Sev1 Incidents, 11 critical alerts, 1 outage → risk score of 27
• Monthly compliance period selected based on risk concentration and alert volume
• Data source: 15 alerts analyzed (full dataset available)

[SLO Configuration]
• Service classified as Most Critical → 99.99% reliability target selected
• Monthly compliance period chosen for consistent tracking of reliability issues
• Duration SLO type selected for continuous measurement of reliability
• SLI type: Errors - keywords and patterns found in 80% of alerts, with additional latency and availability issues identified
• Source: em_alert (alerts provide granular signal for reliability tracking)

[SLIs Created]
• 10 SLIs created covering 100% of reliability events (15 of 15 alerts):
1. Webhook Delivery Failure Rate (main CI sys_id: <sys_id>)
- Tracks critical webhook delivery failures
- 2 alerts matched (13% of total events)
- All events led to service downtime
- Filter: metric_name=Webhook_Delivery_Failure_Rate^classification=webhook_failure^severity=critical
- Example: Alert <alert_id>
2. Data Contract Violation Rate (main CI sys_id: <sys_id>)
- Tracks critical data contract violations
- 2 alerts matched (13%)
- Example: Alert <alert_id>

[Additional SLIs follow the same pattern for each reliability issue identified]

• All reliability events are covered by the SLIs created.

Created by Now Assist SLO Creator Agent

    O que Fazer Depois

    To learn more about SLOs, including SLO types and compliance periods, see Working with reliability metrics. To edit or deactivate an SLO in SRM, see Edit a reliability metric.