Billing Events
Billing events show what exactly generated billable usage inside VARICON.
They provide an event-level view of anomaly intelligence activity, similar to a billing log or usage ledger.
Event log summary
- Each event explains a concrete unit of anomaly usage activity
- Billable events begin after enrichment crosses the metering boundary
- Free events help explain why not all anomaly activity is charged
Why billing events matter
A summary tells you how much was billed.
A billing event stream tells you:
- what happened
- when it happened
- which service generated the event
- which fingerprint contributed to billable usage
- whether an event was billable or free
This makes billing explainable.
What a billing event represents
A billing event is created when anomaly processing crosses the intelligence boundary.
A typical event includes:
- timestamp
- service
- environment
- fingerprint
- event type
- occurrence count
- billable status
This creates a transparent bridge between anomaly detection and spend.
Event types
Typical billing events include:
enriched_anomalyfree_allowance_appliedusage_summary_rollup
In the current public model, the most important event type is:
enriched_anomaly
because it represents the billable unit.
How to use this view
Engineering
Use billing events to identify:
- repeated fingerprint activity
- noisy services
- unstable endpoints
- unexpected enrichment spikes
Platform
Use billing events to understand:
- service-level usage concentration
- environment-specific spikes
- regression-related billing bursts
Finance
Use billing events to audit:
- billable anomaly streams
- recurring usage drivers
- cost transparency over time
Relationship to other billing views
Billing events complement:
Use the dashboard for aggregate visibility.
Use billing events when you need a ledger-like explanation of usage.
Summary
Billing events make usage transparent.
They show not only:
what you were billed
but also:
what produced the billable usage.