What it is for
Proving the belt moves, without waiting for a real error. This is the screen you open right after installing, after touching a plugin, and when someone says "I am not getting alerts".
The sample
One click creates a fake error, with occurrences, customer, version and a stack. It goes through the whole belt: in, read, stored, grouped. From then on every screen has something to show.
Delete the sample removes it and everything it created. No leftovers in the production database.
Firing an event
Pick the event (erro_novo, regressao,
url_fora, whichever) and meulog fires it for real,
through the channels that are on, with the rules in force. It is the test that proves
the whole path, and not just the Slack token.
The message lands in the real channel. Tell whoever is there before using this on an on-call channel.
The state of each part
The screen lists everything that is on and what each part listens to. A part that is on but missing required configuration shows up flagged: it is in the path and it is not going to work.
Difference from the rule dry run
The rule dry run answers "who would be notified" without notifying anyone. This screen notifies. Use the dry run to understand the configuration, and the firing to prove the channel works.