Weik.io

Events

View, search, and manage events in your system

The Events page shows what is flowing through Weik.io in real time. Use it to inspect, search, and debug event traffic without digging through separate system logs.

What are events?

Every event in Weik.io is a standard CloudEvent, with no proprietary wrappers. Each event is a predictable message containing:

  • type: What happened (for example, io.weik.file.created).
  • source: Where the event came from.
  • id: A unique identifier, useful for tracking duplicates.
  • time: When the system recorded the event.
  • datacontenttype: How to parse the body. This is almost always application/json.
  • data: The payload.

Viewing events

The Events UI provides a live view of the stream, showing the type, source, and timestamp of each event. You can open any event to see the raw JSON payload. This is usually the quickest way to verify that an external system sent the data you expected.

Searching events

At high volume, the real-time view becomes hard to follow. Use filters to narrow down the results:

  • Event type: Look for specific occurrences.
  • Time range: Limit results to a specific period.
  • Source: Isolate events from a single API or webhook.

Common uses

The Events page is most often used for debugging. When a downstream system reports missing data, check the event log first: if the event is in the log, Weik.io received it; if it is not, the source system never sent it. The page is also useful for auditing activity and monitoring new integrations during rollout.

How it works

Weik.io persists events in NATS JetStream rather than holding them in memory. This means:

  • Events are written to disk.
  • You can replay events if something breaks.
  • Events respect the limits and retention policies you configure on the stream.

Next steps