Monday, November 16, 2026 · Week 47 DE · EN · FR · ES Dark
AI

Cloud operations: AI automation for stable infrastructure

AIOps detects anomalies and groups events. Data quality, controlled interventions and measurable results are essential.

By Tobias Massow March 3, 2026 3 min read
Cloud operations: AI automation for stable infrastructure

AIOps helps operations teams identify anomalies in cloud environments and interpret related events. Models can take recurring patterns in metrics into account and highlight deviations. A detected anomaly, however, is not yet proof of a cause or an impending outage. For production use, data quality, clear responsibilities and controlled responses are essential.

Key takeaways

  • Anomaly detection complements existing alerts. It can account for time-dependent patterns and report unusual deviations.
  • Event correlation makes triage easier. Related alerts can be grouped, though their common cause still needs to be investigated.
  • Amazon DevOps Guru is approaching end of support. The service has been closed to new customers since 29 October 2026. Existing users should prepare their migration.

Detecting anomalies in context

AIOps stands for Artificial Intelligence for IT Operations. These methods analyse operational data to help teams detect and investigate problems. The data includes metrics and events and, depending on the product, log data. An indication of a deviation is a starting point for diagnosis.

The Datadog Anomaly Monitor, for example, takes trends and recurring daily or weekly patterns into account. This can make a drop in traffic noticeable at a time of day when the same value would otherwise be normal. How sensitively a monitor responds and how much historical data it needs depends on its configuration.

Fixed thresholds remain useful when a known technical or business threshold needs to be monitored. Anomaly detection complements these rules by looking for deviations from previous behaviour.

Grouping events and investigating causes

During an incident, several monitored components may generate alerts. Event correlation groups events according to their relationships or defined rules. This can reduce the number of alerts that need to be reviewed individually.

A shared group does not by itself prove a common cause. Operations teams should be able to check which signals have been grouped and which evidence supports the diagnosis. With DevOps Guru, AWS distinguishes between reactive insights into ongoing problems and proactive insights into predicted problems. A prediction remains an assessment and guarantees neither an outage nor its prevention.

Introducing automation with clear boundaries

A defined service with known responsibilities is a suitable starting point for a pilot. The team can first record existing alerts and handling times, then assess what additional insights the tool provides. Missed incidents and alerts that later prove non-critical are also important.

Automated actions should match the risk associated with the service. A team can initially review recommendations and later authorise clearly defined interventions. The operating plan should include an auditable record and a tested rollback procedure for every automated action. Alongside the product price, the cost assessment should include data ingestion, retention, integration and ongoing maintenance.

Planning for Amazon DevOps Guru end of support

Anyone assessing cloud-native tools must also consider their lifecycle. According to the AWS product documentation, Amazon DevOps Guru has not accepted new customers since 29 October 2026. According to that documentation, existing customers can continue to use the service until 30 September 2027. AWS recommends Amazon CloudWatch for alerts and anomaly detection and identifies Amazon DevOps Agent as a possible alternative for AI-assisted investigations.

The general AWS overview gives a different date for the end of support. Existing customers should therefore confirm the date with AWS and take API calls, Infrastructure as Code and downstream automation into account during migration.

Frequently Asked Questions

Does AIOps replace existing monitoring?

AIOps analyses operational data and complements existing monitoring. Suitable metrics, clear responsibilities and incident handling procedures are still needed to interpret the results.

How much historical data does a model need?

That depends on the product and the method chosen. For its Anomaly Monitor, Datadog specifies at least three weeks of historical data for weekly seasonality. This does not establish a general requirement for other products.

How can the value of a pilot be assessed?

Before and during the pilot, teams can compare measures including the number of alerts handled, the time taken to start handling them and the time to resolution. False alerts and missed incidents should also be included in the assessment.

Image source: AI-generated (November 2026)

Translated from the German original using artificial intelligence. The German version is authoritative.

Also available in

FrançaisEspañolDeutsch
MBF Media Newsletter

The monthly briefing for decision-makers

Once a month, the MBF Media Newsletter gathers what matters from cloudmagazin, MyBusinessFuture, Digital Chiefs and SecurityToday, curated by the editorial team.

Around 23,500 IT and business decision-makers read this newsletter. Read along.

Subscribe for free
MBF Media Newsletter, aktuelle Ausgabe auf dem iPhone
A magazine by Evernine Media GmbH