LogoLogo
  • Getting Started
    • Introduction to OneLens
    • Operational Cost of OneLens
    • Onboarding Guide
    • Accessing OneLens
  • Integrations
    • Cloud Services
      • Connect to AWS
    • Kubernetes
      • OneLens Agent
        • Onboarding a K8s Cluster
        • Artifacts
      • Enable Split Cost Allocation for EKS
  • User Guide
    • Observe ( Visibility and Insights)
      • Cost Analyzer
        • Saved Views
      • Cost Watcher
        • Cost Anomaly
      • Data Transfer Cost Reports
    • Optimize (Cost Savings & Recommendations)
      • Saving Dashboard
        • About Potential Savings
        • View Potential Savings
        • About Achieved Savings
        • View Achieved Savings
      • Policy Violations
        • Drill Down into Policy Violations
      • S3 Optimization
        • Detailed View of Buckets
        • Cost & Usage Breakdown
        • S3 Insights
    • Automate
      • Workflows & Automation
        • Triggers
        • Actions
        • Usecases
          • Automating Periodic Cloud Cost Reports
          • Automatically Create Jira Issues for New Tickets
          • Email Notifications of New Tickets
          • Configure Periodic Digests for Pending Tickets
          • Automating Cost Anomalies Email Alerts
          • Escalation of High-Value Pending Tickets
      • Remediations (Runbooks)
        • Install Runbooks
        • Runbook Catalog
          • Delete CloudWatch Alarms in Insufficient State
          • Delete EBS Snapshots for which corresponding volumes are not in use
          • Delete Idle ElastiCache/Memcached Cluster
          • Delete RDS Snapshots older than a specified period of time
          • Delete idle Classic/Application Load Balancers
          • Delete unused EBS Volumes
          • Delete unused Elastic IP
          • Delete unused NAT Gateway
          • Migrate EBS Volumes from gp2 to gp3
          • Set retention period for CloudWatch Logs
        • Execution Logs
    • Govern ( Control & Governance)
      • Cost Optimization Policies
  • Facts & FAQs
    • FAQs
      • Connect Slack Private Channels to OneLens
Powered by GitBook
On this page
  • Use Case
  • Video Guide
  • Setting up Workflow
  • 1. Access Workflow Section in OneLens
  • 2. Create a New Workflow
  • 3. Choose the Trigger for the Workflow
  • 4. Set Up Email Notifications
  • 5. Publish the Workflow
  • Result
  1. User Guide
  2. Automate
  3. Workflows & Automation
  4. Usecases

Automating Cost Anomalies Email Alerts

PreviousConfigure Periodic Digests for Pending TicketsNextEscalation of High-Value Pending Tickets

Last updated 1 month ago

This guide explains how you can set up automatic email notifications for cost anomaly tickets using workflows in OneLens.

Use Case

For instance, you may want your finance or operations team to receive an email alert whenever a cost anomaly is detected with a cost impact greater than $100. This will enable faster investigation into unexpected spending and helps in controlling potential budget overruns.

Video Guide

For a more detailed walkthrough, refer to the video available here.

Setting up Workflow

1. Access Workflow Section in OneLens

  1. Navigate to the workflow section of OneLens.

  2. Click the Create button in the top-left corner to start a new workflow.

2. Create a New Workflow

  1. A dialog box will appear asking for a workflow name. Enter a descriptive name (e.g., “Send Email Alerts for High-Value Tickets").

  2. You can also add a description, which is optional.

  3. Once you’ve filled in the details, click Create to proceed.

3. Choose the Trigger for the Workflow

In the workflow setup, select the Anomaly option as your trigger.

You will then choose the Anomaly is Detected.

Trigger Start

  • You’ll have two options for how these conditions should be applied:

    • Trigger when all conditions match – the workflow will only trigger if all conditions are met.

    • Trigger when any condition matches – the workflow will trigger if one of the conditions is met.

  • You can configure multiple conditions by clicking on the Add Rule button.

Conditions Configuration

Each condition involves filling out three fields:

  1. Criteria: Choose the specific property of the ticket you want to filter by. You can use the following attributes:

    1. Ticket: Cost Impact ($), Cost Impact (%)

    2. Resource: Account, Region, Service

    3. Cost Center (Org Hierarchy): Cost Center, Category

  2. Limit: Set a comparison operator or criteria type for the selected attribute. The available options vary based on the chosen criteria.

  3. Borderline: Set the specific value or list of values to compare against.

Example: Ticket > Cost Impact ($)

  • Criteria: Cost Impact ($)

  • Limit: Greater Than

  • Borderline: 500 (this would filter for tickets where potential savings are greater than $500).

4. Set Up Email Notifications

  • After defining the trigger and conditions, click Add Step.

  • Under Messaging, choose Send Email to Users.

Configure Email

Add the following details:

  • Recipients: Enter the email addresses of the users who should receive the email notifications.

  • Cc/Bcc: Optionally, add additional recipients in the Cc or Bcc fields.

  • Subject: Specify the subject line for the email notification.

  • Message: Enter the email's body content, including relevant details for the recipients.

Preview the Email

To ensure the email looks as expected, you can preview it before sending it.

Click on Show Preview with Mock Data to view the email preview. This will display how the email will appear with sample data, allowing you to verify its format and content.

Once you're satisfied with the preview, click on Save Changes.

5. Publish the Workflow

Review the workflow representation to ensure everything is set up correctly.

Click Publish to make the workflow active.

Result

Here is how your email would look: