Skip to main content
Events add context to cost data. They capture deployments, releases, incidents, provider changes, and business milestones so you can explain why spend changed without switching between billing tools and engineering systems.
Costory Events page showing saved events with filters and context

​
Overview

The Events page is where you search, filter, create, and reopen events across your organization. Each saved event can include context such as the date, source, category, labels, description, and linked cost analysis. Use events when you need to:
  • Save the context behind a cost change
  • Correlate deploys, incidents, and provider changes with spend
  • Attach event context to Explorer views, dashboards, and reports
  • Give finance and engineering the same timeline for cost discussions

​
Event categories

CategoryWhat it representsExamples
BusinessProduct and go-to-market milestonesFeature launch, pricing change, customer onboarding
TechnicalEngineering and infrastructure changesDeploy, incident, migration, CI/CD run
ProviderCloud billing and commitment changesSavings Plan purchase, CUD activation, marketplace renewal
Provider events can be detected from billing data. Technical and business events can come from GitHub, CI/CD pipelines, or the Events API.

​
Create a saved event with context

1

Open Events

Navigate to Events from the left sidebar.
2

Create an event

Click New event and enter the date, title, category, source, and description.
3

Add context

Add labels or scope details that help people understand where the event applies, such as environment = production, a cloud provider, a team, or a service.
4

Save

Save the event so it appears on the Events page and can be added to Explorer charts.

​
Use events in Explorer

Events become most useful when you place them on the same timeline as costs.
1

Open Explorer

Build the cost view you want to explain in Explorer.
2

Enable events

Use the Events control to show relevant events on the chart. Search, filter, or add individual events to focus the timeline.
3

Save the view or dashboard

Save the Explorer view, or turn it into a dashboard, so the event context stays attached for the next reader.
Pair events with waterfall charts. The waterfall shows which services or teams moved. Events help explain what changed around the same date.

​
Find and manage events

From the Events page, you can:
  • Search by title, source, category, label, or date range
  • Open an event to review its description and linked context
  • Add an event to an Explorer chart
  • Edit manually created events when the context changes
For event source setup, use the Events setup guides.

​
Frequently Asked Questions

No. Events are metadata. They explain cost changes but do not modify billing rows, allocation rules, or cost metrics.
Yes. Create an event with a historical timestamp, or post one through the Events API. Costory places it on the correct date in Explorer.
Yes. When events are attached to a saved Explorer view or dashboard, the context can appear in scheduled reports that use that view.

​
Next Steps

Explore with context

Overlay events and metrics on cost charts

Events setup

Connect GitHub, CI/CD, provider, and API event sources

Explorer

Investigate cost changes with event context

Event Correlation use case

Walk through cost change investigations with events
Last modified on June 24, 2026