randarium
Datasets

Event Stream Data Generator

Create realistic event stream data in CDC (Change Data Capture), Kafka, telemetry, or clickstream styles. Each style has appropriate event types and operations. This data is synthetic and not real.

Also known as: event logs · streaming data · event tracking

seeded · synthetic data

Output

No output yet — set your options and hit .
About this tool, tips & examples

What it does

The Event Stream Data Generator produces realistic streaming-event fixtures in four styles: CDC (Change Data Capture) records with inserts, updates, and deletes; Kafka-style messages; telemetry events; and web clickstream data. Generate up to 100,000 events from a chosen start date, seeded so the exact same stream can be replayed, and export as JSON, NDJSON, CSV, TSV, or Markdown.

Common use cases

  • Stream-processing pipelines — NDJSON event batches to push through Kafka consumers, Flink jobs, or serverless handlers in development.
  • CDC testing — insert/update/delete change records for exercising sync jobs, upsert logic, and tombstone handling.
  • Analytics development — clickstream and telemetry data for building funnels, sessionization, and dashboards before real traffic exists.
  • Load and soak tests — 100k reproducible events per run, regenerable on any machine from the seed.

Settings

  • Style — CDC, Kafka, telemetry, or clickstream; each emits the event types and operations appropriate to that world.
  • Events — 1 to 100,000 per run.
  • Start date — the timeline the event timestamps advance from.
  • Seed — the same seed and settings reproduce the identical stream — byte-stable fixtures for integration tests.

Privacy note

Events are generated locally in your browser and never uploaded. Everything is synthetic — fabricated users, actions, and records — so it can flow through logs and dashboards without any privacy concern, and must not be presented as real traffic.

FAQ

Which format should I export? NDJSON for anything stream-shaped (one event per line pipes straight into most tooling); CSV/TSV for spreadsheet analysis; JSON when a single array is easier to load.

Are the timestamps ordered? Events advance from your start date like a real stream, so time-window logic (sessionization, tumbling windows) has something meaningful to chew on.

Can I regenerate the same stream in CI? Yes — pin the seed, style, count, and start date, and every environment generates the identical events.