Features

See cost through the lens of your deployments.

Events let you mark significant moments in your delivery lifecycle — deployments, releases, campaign launches, configuration changes — so you can instantly correlate them with shifts in Azure resource usage and cost.

cirrova — Events

Tenant

All

Mark what matters.

Create point-in-time events for deployments, releases, infrastructure changes, campaign launches, and more. Each event is timestamped and scoped to a tenant so it appears in the right context.

Correlate events with cost changes.

Events are surfaced alongside your cost and anomaly data. When a cost spike appears, you can see at a glance whether a deployment or campaign launch coincided with it — no more guessing what changed.

Automate via the Cirrova API.

Use the Cirrova REST API to create events automatically as part of your CI/CD pipeline. A single API call from a GitHub Action, Azure DevOps pipeline, or any deployment tool is all it takes.

Categorise and filter.

Organise events by category — Deployment, Release, Campaign, Configuration, and more. Filter by tenant, category, tag filter, or date range to focus on exactly the period you're investigating.

Scope events to specific resources.

Optionally attach a tag filter (e.g. Platform = Nextron) to an event. On resource and resource group detail pages, cost history charts surface only events whose tag matches the resource — or universal events that apply to all. Events with no tag filter are always shown.

Per-tenant scoping.

Events are scoped to a specific Azure tenant, so each team or customer sees only the events relevant to their environment. One platform, cleanly separated context per tenant.

Secure API access.

Events are created using scoped API keys with the minimum required permissions. Store your key as a CI/CD secret and rotate it at any time from within Cirrova — no downtime required.

CI/CD Integration

Record a deployment in one step.

Add a single step to your GitHub Actions workflow to automatically create a Cirrova event every time you deploy — so cost context is always up to date without any manual effort.

.github/workflows/deploy.yml

YAML

- name: Record deployment in Cirrova
  if: success()
  env:
    CIRROVA_API_KEY: ${{ secrets.CIRROVA_API_KEY }}
  run: |
    curl -s -X POST https://api.cirrova.io/v1/events \
      -H "Authorization: Bearer $CIRROVA_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{
        "title": "Deployed to production",
        "description": "Build ${{ github.run_number }} — ${{ github.sha }}",
        "category": "Deployment",
        "occurredAt": "${{ github.event.head_commit.timestamp }}"
      }'

Store your API key as a secret

Add CIRROVA_API_KEY to your repository or organisation secrets. Never hard-code credentials in workflow files.

Works with any CI/CD tool

The Cirrova Events API is a standard REST endpoint. Use it from GitHub Actions, Azure DevOps, Bitbucket Pipelines, Jenkins, or any script that can make an HTTP request.

Appears in Cirrova immediately

Events are visible in the Cirrova UI as soon as they are created. No polling delay — your deployment is recorded the moment the pipeline step runs.

Related Features

Events are most powerful alongside these capabilities.

Know exactly what changed — and when.

Correlate every deployment and release with your Azure cost data automatically.

Start Free Trial Book a Demo