Repository navigation
Exports and Reports
Ratomir Jovanovic edited this page Oct 25, 2026
·
1 revision
Every analysis can be exported. Exports are generated locally and downloaded directly; nothing is uploaded.
| Format | Use |
|---|---|
| JSON | machine-readable report for tools, tests or archives |
| Markdown | readable report for a ticket, pull request or chat |
| PNG | an image of the timeline for slides or quick sharing |
- tool name and version, rule catalog version and adapter versions,
- detected providers and formats, with confidence,
- normalized events (only safe fields),
- decoded errors,
- correlation groups,
- findings with evidence, recommended action and limitations,
- a redaction section stating that identifiers are masked and sensitive fields are excluded,
- warnings, for example ambiguous detection or removed keys.
Identifiers are masked by default. Masked values keep a short prefix and suffix so you can still match them against your own logs. Use the explicit option to include full identifiers only when you trust the recipient.
- Prefer the Markdown export for support tickets. It is short and safe by default.
- Mention the rule catalog version when you discuss a finding, because rules can change between releases.
PandaPayLens is open source under the Apache-2.0 license. Demo · Repository · Changelog
Using PandaPayLens
- Getting Started
- Input Formats
- Error Decoding
- Timeline and Correlation
- Diagnostic Rules
- Exports and Reports
- Command Line Interface
Providers
Under the hood
Community