e-volv

Performance playbook

CloudCostAnomaly

Weekly billing anomaly detection correlated against infrastructure changes and deploys to name the change most likely causing a spike.

Once a week, pulls cloud billing broken down by service and SKU, detects anomalies against a trailing baseline, and correlates each spike against infrastructure changes and deploys in the same window. Files a ticket naming the change that most likely caused each regression.

Identifier
cloud-cost-anomaly
Version
1.0.1
Steps
5
Triggers
1
  • cloud
  • cost
  • anomaly
  • billing
  • infrastructure
  • weekly

When it runs

Scheduleschedule.weekly
Schedule
Every Monday at 07:00 UTC 0 7 * * 1
Timezone
UTC

The pipeline

The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.

React Flow
  1. 01
    Weekly Schedule (Monday 07:00 UTC)trigger

    The event that starts the run.

  2. 02
    Fetch Billing Data ⚠️ SET YOUR BILLING ACCOUNThttp.request

    Calls an external HTTP endpoint with vault-resolvable headers.

  3. 03
    Clone Infrastructure Repository ⚠️ SET YOUR REPOgit.clone

    Shallow-clones the repository at the right ref.

  4. 04
    Analyse Cloud Cost Anomaliesagent.run

    One agent works the task with its toolkit.

  5. 05
    File Cost Anomaly Ticketticket.create

    Opens a ticket on the connected tracker.

The agent

Cloud Cost Analyst

Base type
Senior Developer
Temperature
0.2
Max iterations
40
Tools
7

Memory · 2

  • memory_writeWrite Memory · write
  • memory_readRead Memory · read

Terminal · 1

  • run_terminal_cmdRun Terminal Command · write

Filesystem · 1

  • read_fileRead File · read

Code search · 1

  • code_searchCode Search · read

Tickets · 1

  • create_ticketCreate Ticket · write

Status · 1

  • update_statusUpdate Status · write