Monedula
Kafka Simulator docs menu

Report an issue

Open the public issue tracker from the playground's ⋯ menu, and give us a link and a build number we can reproduce the problem from.

How-to guides 10 of 10

1 min read

Updated 17 October 2026

Markdown

On this page

Before you start

  • A GitHub account, to file the issue on GitHub.

Steps

Go to the frame where the problem shows, then select Share link in the top bar to copy a link to it. The link holds the scenario, the frame and every action you took. Share a session as a link explains what it carries.

2. Note the build

The ⋯ menu in the top bar names the build next to the modeled Kafka version, as build · followed by the version, for example build · 1.9.0.

3. Open the issue tracker

Open the ⋯ menu at the right of the top bar and select report issue, marked with a ⚐ flag, under report. It opens the issue list of the monedula-kafka-simulator-issues repository on GitHub in a new tab.

The button is a plain link, opened with noreferrer: it sends nothing about your session, not even the playground address.

4. Write the report

File a new issue there and include:

  • the link from step 1;
  • the build from step 2;
  • what you expected to happen and what happened instead, naming the tab or the Inspector view where you saw it.

Check it worked

Open your link in a private window: if it replays the problem, we can too.

  • Fidelity lists what the simulator models and what it leaves out, which helps tell a bug from a known limit.