High level DevOps Guru workflow - Amazon DevOps Guru

High level DevOps Guru workflow

The Amazon DevOps Guru workflow can be broken down into three high level steps.

  1. Specify DevOps Guru coverage by telling it which AWS resources in your AWS account you want it to analyze.

  2. DevOps Guru starts analyzing Amazon CloudWatch metrics, AWS CloudTrail, and other operational data to identify problems that you can fix to improve your operations.

  3. DevOps Guru makes sure that you know about insights and important information by sending you a notification for each important DevOps Guru event.

You can also configure DevOps Guru to create an OpsItem in AWS Systems Manager OpsCenter to help you track your insights. The following diagram shows this high-level workflow.

Coverage, insights, and notification integration in a DevOps Guru workflow.
  1. In the first step, you choose your coverage by specifying which AWS resources in your AWS account are analyzed. DevOps Guru can cover, or analyze, all the resources in an AWS account, or you can use AWS CloudFormation stacks or AWS tags to specify a subset of the resources in your account to analyze. Make sure that the resources you specify make up your business critical applications, workloads, and micro-services. For more information about the supported services and resources, see Amazon DevOps Guru pricing.

  2. In the second step, DevOps Guru analyzes the resources to generate insights. This is an ongoing process. You can view the insights and see the recommendations and related information they contain in the DevOps Guru console. DevOps Guru analyzes the following data to find issues and create insights.

    • Individual Amazon CloudWatch metrics emitted by your AWS resources. When an issue is identified, DevOps Guru collects those metrics together.

    • Log anomalies from Amazon CloudWatch log groups. If you enable log anomaly detection, DevOps Guru displays related log anomalies when an issue occurs.

    • DevOps Guru pulls enrichment data from AWS CloudTrail management logs to find events that are related to the collected metrics. The events can be resource deployment events and configuration changes.

    • If you use AWS CodeDeploy, DevOps Guru analyzes deployment events to help generate insights. Events for all types of CodeDeploy deployments (on-premises server, Amazon EC2 server, Lambda, or Amazon EC2) are analyzed.

    • When DevOps Guru finds a specific pattern, it generates one or more recommendations to help mitigate or fix the identified issue. The recommendations are collected in one insight. The insight also contains a list of the metrics and events that are related to the issue. You use the insight data to address and understand the identified problem.

  3. In the third step, DevOps Guru integrates insight notification into your workflow to help you manage issues and quickly address them.

    • Insights generated in your AWS account are published to the Amazon Simple Notification Service (Amazon SNS) topic chosen during DevOps Guru setup. This is how you are notified as soon as an insight is created. For more information, see Updating your notifications in DevOps Guru.

    • If you enabled AWS Systems Manager during DevOps Guru setup, each insight creates a corresponding OpsItem to help you track and manage the issues discovered. For more information, see Updating AWS Systems Manager integration in DevOps Guru.