AT:
- an event has the following fields:
id (global UID)
eventName
timestamp (ms)
traceId
duration (optional)
group (optional)
source (optional)
payload (optional) - generic Json payload - there is a REST API to ingest events
- it allows ingesting a single event
- it allows to ingest a batch of events
- there is a configurable secret for the even ingestion endpoint that needs to be provided on ingest, otherwise any request is rejected with a 401
- there is a configurable max batch request size (as it affects optimize heap memory)
- events get persisted into a dedicates event index
- no API documentation yet, will be handled with
OPT-2823