Skip to content

Event Explorer

Event Explorer lists the business events Plutus has imported from your connected event sources — deploys, incidents, releases, customer onboarding/churn, and subscription changes — in one timeline, separate from cost data.

Each event has a source, a type, and a timestamp. What you see depends on which event sources you’ve connected:

  • Releases and deploys — GitHub releases and PRs, Vercel production deploys, Linear issue creation.
  • Incidents and reliability — PagerDuty incidents, Sentry newly reported errors.
  • Business events — Jira, GitLab, Salesforce client onboarding and churn, Stripe subscription created/canceled.

An event source that isn’t connected contributes nothing — Event Explorer doesn’t show placeholder rows for sources you haven’t added. See Sources & integrations for the full list of event sources and how to connect one.

Use the source filter to narrow the timeline to one or more event sources — for example, just PagerDuty incidents, or just Stripe subscription events. Combine it with the date range to check whether an incident or deploy happened before or after a specific cost change.

The same events show up as markers on the cost charts elsewhere in Plutus — the Dashboard’s trend charts and the Cost Explorer’s timeline both support overlaying the event timeline on top of the cost line. Hovering a marker shows the event’s source, type, and timestamp without leaving the chart.

This is the main use of the timeline: correlating a spend spike with what happened around the same time. For example, if daily AWS spend jumps on a Tuesday, overlaying events can show whether a production deploy landed that day, whether a PagerDuty incident triggered autoscaling, or whether neither did — in which case the cause is somewhere else.

Event Explorer itself has no cost data in it — it’s the timeline on its own, without a chart behind it. Use it when you want to scan or filter events directly rather than read them off a chart.