From 55ee0449e2dd327c2f5d4d218a0fe9d333c4dde4 Mon Sep 17 00:00:00 2001 From: Elinor <106514736+elinornetapp@users.noreply.github.com> Date: Thu, 5 Dec 2024 21:54:34 +0200 Subject: [PATCH] Lnr1029 (#5131) * Update anomaly-detection.md * Update README.md --- .../tutorials/workflow-builder/README.md | 8 +++++-- .../workflow-builder/anomaly-detection.md | 23 ++++++++++--------- 2 files changed, 18 insertions(+), 13 deletions(-) diff --git a/src/docs/cost-intelligence/tutorials/workflow-builder/README.md b/src/docs/cost-intelligence/tutorials/workflow-builder/README.md index f2ec4b423..6e202a456 100644 --- a/src/docs/cost-intelligence/tutorials/workflow-builder/README.md +++ b/src/docs/cost-intelligence/tutorials/workflow-builder/README.md @@ -1,6 +1,10 @@ # Workflow Builder You can create automated workflows in Cost Intelligence Workflow Builder. Flows are based on data in the Cost Intelligence dashboards. +## Prerequisites + +An alert or action based on automatically identified anomalies (must be indicator, dial or bullet). + Here are some examples of types of flows you can create: * Send scheduled emails * Generate alerts based on specific conditions @@ -14,7 +18,7 @@ Here are some examples of types of flows you can create: ## Create a Workflow -1. Click Create New Flow. +1. Click **Create New Flow**.
View image @@ -97,7 +101,7 @@ Here is a simple example of an SMS sent once a day for 3 days. It includes the m ## Edit an Existing Workflow -To edit an active flow, click **Pause**, then you can make your changes. +To edit an active flow, click **Pause**. ## Tokens diff --git a/src/docs/cost-intelligence/tutorials/workflow-builder/anomaly-detection.md b/src/docs/cost-intelligence/tutorials/workflow-builder/anomaly-detection.md index d0b6a43b1..5155d3247 100644 --- a/src/docs/cost-intelligence/tutorials/workflow-builder/anomaly-detection.md +++ b/src/docs/cost-intelligence/tutorials/workflow-builder/anomaly-detection.md @@ -18,33 +18,34 @@ Create a metric in the **Cost Intelligence** dashboards. The example below shows how to generate a metric that identifies the percentage change of compute resources for a specific AWS region, comparing a day to its previous week. 1. On the left panel, click the **Billing** dataset. +2. On the right panel, click the Indicator chart Anomaly-indicatorChart. + +**Note**: The metric must be one of the three chart types: indicator, dial or bullet. Anomaly1 - -3. On the right panel, click the Indicator chart Anomaly-indicatorChart. -4. On the left panel, drag **ServiceCategory** to the Values field. +3. On the left panel, drag **ServiceCategory** to the Values field.
View clip
-5. In the Values field, click the three vertical dots kebab and select **Distinct Count**. -6. In the menu in the right panel, click **Comparison**. The Date Column field opens. From the left panel, drag **BillingPeriodStart** into the Date Column field. +4. In the Values field, click the three vertical dots kebab and select **Distinct Count**. +5. In the menu in the right panel, click **Comparison**. The Date Column field opens. From the left panel, drag **BillingPeriodStart** into the Date Column field.
View clip
-8. Select the two time periods to compare between in the Time Period field and the Comparison field. In this example: +6. Select the two time periods to compare between in the Time Period field and the Comparison field. In this example: * **Time Period**: select Today. * **Comparison field**: select Last Week. -9. Make sure that the **Type** is percent **%**. +7. Make sure that the **Type** is percent **%**. -10. You can add a number of filters. For example, you can filter on provider, specific regions, and service category: +8. You can add a number of filters. For example, you can filter on provider, specific regions, and service category:
  1. In the right panel, click Filters.
  2. @@ -63,9 +64,9 @@ The example below shows how to generate a metric that identifies the percentage
-11. Click the Untitled Chart field and enter a unique name for the metric, such as **Anomaly—AWS Compute US-East**. -12. Click **Save**. The workflow is added to the dashboard. -13. Click **Publish Dashboard**. The metric is prepared for the workflow builder to create an anomaly alert. +9. Click the Untitled Chart field and enter a unique name for the metric, such as **Anomaly—AWS Compute US-East**. +10. Click **Save**. The workflow is added to the dashboard. +11. Click **Publish Dashboard**. The metric is prepared for the workflow builder to create an anomaly alert. ## Step 2: Create an Anomaly Detection Workflow