Text events and severity
Report short events with a timestamp and severity instead of uploading full logs.
On this page
What you need
A monitor and its device key.
How to do it
- Choose info, warning or critical and write a short message describing the event.
- Send the message to /api/v1/ingest/events with a stable event ID and timestamp.
- Check the event in the monitor. Create a text or severity rule if you want notifications.
Good to know
The message may use at most 2 KiB of UTF-8 text; the entire event may use at most 4 KiB. You can use up to ten labels with a combined size of 2 KiB. Keep secrets and personal content out of messages and labels.
Retry with the same ID and unchanged content. Full messages expire after seven days; older summaries show counts.
If something goes wrong
Check the event allowance separately from the shared data allowance. If the same ID has different content, correct the conflict instead of retrying unchanged.
Related guides
- Text and event rules
Find relevant words or severity levels in short event messages.
- Workflows and parallel runs
Follow each workflow or AI-agent execution, including simultaneous runs.
- Archive queries and downloads
Wait for longer history queries and download their results when ready.