Events Overview
Events are structured records of discrete developments in the systems each product tracks.
What is an Event?
An Event captures a specific market occurrence such as an outage, policy change, or supply disruption in a structured format. Events are designed to:
- Provide systematic tracking of market-moving developments
- Enable quantitative analysis of event impacts
- Support timely alerting and historical research
Event Structure
Each event includes:
| Field | Description |
|---|---|
event_key | Unique identifier, an MD5 of type, date and scope |
event_date | The date the event fired |
event_type | Category, for example GBSI_REGIME_SHIFT |
event_name | Human-readable label |
event_tier | Severity tier |
event_direction | Direction of the change, where one applies. (Not served on GBSI-US, GBSI-EU and GLMI events, which record a change of state, not a price side) |
magnitude_score | Size of the move that triggered it |
magnitude_bucket | Banded magnitude |
str_effective_at | When the event became publicly knowable |
str_observed_at | When Snowtrail could first have held it |
str_ingested_at | When this row was written |
An event fires on a transition into a state, not on every day the state holds, so consecutive-day duplicates are not expected.
Event status and data revisions
GBSI-US, GBSI-EU, GLMI and WSSI-US events carry an event_status column. When a source
revision means a transition no longer occurs, the event is not deleted: it is
written as a new version with event_status = 'SUPERSEDED', and
superseded_by_source (for example DATA_REVISION) and superseded_at record
why and when. Filter on event_status = 'ACTIVE' for the current event set; the
original version stays reachable through as_of.
Event Categories
Events are organised by type:
- Outages - Unplanned supply disruptions
- Maintenance - Scheduled maintenance activities
- Policy - Regulatory or policy changes
- Weather - Weather-related disruptions
- Infrastructure - Capacity or infrastructure changes