Use Diagnostics and Replay

Before you start

• Open the source you want to validate.
• Save your latest mapping and routing changes first.

Do this

1. Open the source and review Diagnostics to see how Beacon is parsing the payload and provider profile.
2. Check for missing field paths, unmapped severity values, or binding errors before you replay.
3. Open Replay and run the saved sample back through the source.
4. Inspect the replay result and confirm the generated alert summary, scope, environment, and dedupe behavior.
5. If the result is wrong, return to Mapping or Routing, fix the paths, and replay again.
6. Use replay until the output matches what you want operators to see during a live event.

Check it worked

• Replay produces the alert you expected.
• Diagnostics no longer show the field or binding issues you were chasing.
• You can explain how the source will behave before sending it live.

If it does not work

• If replay fails immediately, make sure the source still has a valid sample attached.
• If field mapping looks partially correct, fix one field at a time and replay after each change.
• If the provider profile is wrong, correct that first because diagnostics will be misleading otherwise.

Next

• Review Beacon suggestions
• Build ownership mappings