Event Streams
Last updated
Was this helpful?
Developers
Last updated
Was this helpful?
KORE event streams allow you to stream event data to your existing system by configuring destinations.
Event streams are and broken down as follows:
- Where the events go
- Defines what events to send to which destination
- The events you can stream
- Defines how the schema is organized for each event type
To get started right away, you can review the and one of our quick start guides:
Please be aware of the following aspects and limitations of event streams:
In case of delivery failure, our system implements an auto-retry mechanism. We will attempt to resend the events to your destination up to three times with an exponential back-off strategy. This approach progressively increases the delay between each retry attempt, reducing network congestion and improving the likelihood of successful delivery.
To prevent request timeouts, ensure that your webhook destination responds with an acknowledgment as quickly as possible, the maximum timeout of a request is up to 5 seconds. Implement efficient processing and consider asynchronous handling for time-consuming operations to maintain responsiveness.
A single request may contain multiple events. Our system employs a batching mechanism for efficiency. If several records for the same event type are generated within a brief interval, they will be consolidated into a single request up to a maximum of 50 records.
The system does not guarantee the order in which events are delivered. Consequently, users should not rely on the sequence of event reception for processing logic. Instead, it is crucial to utilize the event timestamp to accurately determine the chronological order in which events were originally generated.
KORE Event Streams are free to use.
For more details on preventing request timeouts with webhooks, refer to our .
Duplicate records may occur due to retry mechanisms or system failures. To maintain data integrity and prevent redundant processing, implement a de-duplication strategy. All cloud events include a property, which serves as a unique identifier for de-duplication. We recommend leveraging this property to handle duplicate records efficiently. By implementing this approach, you can ensure the consistency and reliability of your event processing.