Events
View, search, and manage events in your system
When integrations break, you usually spend hours digging through disparate system logs trying to figure out where a payload went wrong. The Events page exists to fix that. It shows exactly what is flowing through Weik.io right now.
What are Events?
In this system, every event is a standard CloudEvent. No proprietary wrappers, no guessing what fields are called. When something happens, you get a predictable message containing:
type: What actually happened (likeio.weik.file.created).source: Where it came from.id: A unique identifier so you can track duplicates.time: When the system recorded the event.datacontenttype: Almost alwaysapplication/json, but tells you how to parse the body.data: The actual payload you care about.
Viewing Events
The Events UI isn’t complicated. It gives you a live look at the stream, showing the type, source, and timestamp. You can click into any event to see the raw JSON payload. This is usually the quickest way to figure out if an external system sent you the data you actually asked for.
Searching Events
If you have high volume, the real-time view becomes useless quickly. You can narrow down the noise using filters:
- Event Type: Look for specific occurrences.
- Time Range: Find out what happened last Tuesday at 2 AM.
- Source: Isolate a noisy API or a broken webhook.
Why Look at This?
Most developers use this page for debugging. When a downstream system complains about missing data, you can check here first. If the event is in the log, Weik.io received it. If it isn’t, the source system never sent it. It’s also a straightforward way to audit activity or monitor new integrations during rollout.
How it Actually Works
Weik.io doesn’t just hold these events in memory. They hit NATS JetStream, which means:
- The events are actually written to disk.
- You can replay them if something breaks.
- They respect whatever limits and retention policies you set up on the stream.
What’s Next
- Eventing Overview - See how the pieces fit together
- Streams - Manage how long events stick around
- Event Sources - Bring data into the system
- Event Channels - Push data out