Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Overview

The SAP Cloud ALM Status Events Input extracts and collects status events related to services belonging to business services. These status events include disruptions, degradations, and maintenance activities. The events can either be reported by SAP for Me and transferred to SAP Cloud ALM or created directly within SAP Cloud ALM. By collecting these events, users can gain insights into the health and availability of critical business services.

Data Collected

The SAP Cloud ALM Status Events Input collects the following types of events:

  1. Service Degradation Events

    • Events indicating reduced performance or partial outages of business services.

    • Includes details such as the affected service, start and end times of degradation, and severity level.

  2. Service Maintenance and Planned Outage Events

    • Tracks scheduled maintenance activities and planned outages.

    • Provides information on impacted services, maintenance windows, and expected downtime.

  3. Service Disruption Events

    • Captures unplanned service disruptions and outages.

    • Includes root cause analysis (if available), time of occurrence, and service recovery details.

  4. Custom Status Events

    • User-defined events created within SAP Cloud ALM for internal service monitoring.

    • Enables users to track custom incidents and correlate them with other metrics.

Use Cases

  1. Proactive Service Monitoring

    • Gain visibility into service health and identify potential degradations or disruptions before they impact business operations.

  2. Planned Maintenance Management

    • Monitor and plan around scheduled maintenance events to minimize business impact.

  3. Incident Correlation and Analysis

    • Correlate status events with other performance and usage metrics to analyze the root cause of issues and resolve them effectively.

  4. Service-Level Agreement (SLA) Compliance

    • Track service disruptions and degradations to ensure compliance with SLAs and identify areas for improvement.

  5. Historical Trend Analysis

    • Use collected events to analyze historical data for recurring issues, enabling predictive maintenance and capacity planning.

Status

Available

  • No labels