Event Store

The Event Store is a versatile data storage solution in the mediation system, enabling data ingestion, storage, and processing for various scenarios such as multi-region data collection, time-shifted processing, and data validation.

The Event Store is an intermediate data storage solution in the mediation system that serves as both a source to ingest data and a target to store event data. You can add an event store to a custom meter to capture, store, and process event data.

The Event Store UI displays a sampled preview of records and is intended for quick inspection rather than exhaustive validation. Because filters in the UI operate on the previewed sample, a record might exist in the Event Store even if it does not appear in the current UI results. If you need authoritative verification of whether a record was stored, use the Event Store data APIs to query the underlying event data directly.

The Event Store can be used in the following scenarios:

Business need	Using the Event Store
Multi-region data collection and business consolidation	You can use the Event Store to collect data from different geographic regions that may generate data at different times, the Event Store can serve as a central repository before processing the aggregated data. The Event Store collects data from all regions as it becomes available throughout the month, then a single meter pulls from the Event Store to process the consolidated data once all regions have reported. Example: A global company has operations in Asia, Europe, and North America. Each region has its own billing system that generates usage data. The company needs to consolidate all this data before processing it for customer invoicing.
Time-shifted processing	You can use the Event Store to ingest data at one time but process it at a later point (e.g., collecting usage throughout the month but only processing at month-end)
Data transformation	You can use the Event Store to collect data in different formats for subsequent processing, the Event Store can serve as the intermediary storage.
Error recovery and reprocessing	If there are issues with downstream processing, having data in the Event Store allows for data reprocessing without needing to re-extract from source systems.
Data validation	You can use the Event Store to verify data completeness or correctness before submitting it for billing or other critical processes.
Usage-based Pricing with Verification	You can use the Event Store to collect the raw usage events, then at month-end, run a verification process before determining the final billable amount. Example: A SaaS provider charges customers based on API usage. They want to collect raw usage data throughout the month, but need to verify and clean the data before calculating charges.
Regulatory Reporting with Historical Access	You can use the Event Store to store all communication events in the Event Store. Use that data to generate monthly compliance reports while maintaining the ability to query data during the billing cycle, before pushing that data into a data warehouse. Example: A telecom company must maintain records of all customer communications for regulatory purposes.

You cannot select the same event store as different output targets for the same meter.
You cannot use the same event store as both a source and target in the same meter.

When designing Event Store schemas, use numeric fields only for values that fit the supported decimal precision and scale. Event Store numeric fields support precision 22 and scale 9, which allows up to 13 digits before the decimal point and 9 digits after it. If large identifiers such as trade IDs or deal IDs can exceed that limit, store them as STRING values instead of numeric fields. STRING is text-based, supports up to 255 characters, and UniqueKey is also a string field type.

Click the Event Store button on the Meters landing page to see the list of event stores. Click on an event store name to see the details.

To create an event store, click Create New Event Store, and enter a name. Select the required event definitions or if a required event definition is not available, you can create or import one.

To clear (truncate) an event store, click the more actions (…) icon for the event store, and click Clear Event Store. You can also click Clear Event Store on the event store details page. If the event store is linked to meters that are in use, unlink all meters before clearing the data. Clearing an event store permanently deletes all events stored in it and cannot be undone. This eliminates the need for API access to truncate an event store and is particularly useful when you want to reuse an existing event store without retaining its previously stored data.