Skip to content

Support bundle & feedback path

If none of the other troubleshooting guides lead to the cause, a support bundle is the fastest way to give us the information we need — without you having to hunt down logs and redact secrets by hand.

Build a support bundle

Admin → Maintenance → Support Bundle (requires super admin permission).

The bundle is deliberately a full diagnostic — it includes everything needed to understand a bug: versions, system health, RAM/disk/load, Docker container state (status, restarts, OOM events, image tags), database and Redis statistics, the state of the check pipeline, all currently non-OK checks with their effective configuration, hosts/collectors/agents, the latest diagnostic events, the notification log, error summaries, raw logs, configuration values (sanitized), and the migration state. The only hard boundary is: real secrets never go in — tokens, passwords, private keys, and similar values are detected and masked automatically before packaging. If the check still finds a match afterward, the whole bundle is discarded rather than sent partially redacted.

Before sending: deselect sections

You don't have to include everything. Before sending or downloading, you can:

  • deselect individual sections (e.g. leave out raw logs if you only want to show the pipeline state)
  • add a short description — what's the problem, what have you already tried

The version actually sent is run through the masking check again server-side — even if you edited sections manually before sending.

Send or download

  • Send — goes directly to the licence portal, ends up in our diagnostics view there
  • Download — save it locally as a file, e.g. to send by mail to hello@vesana.org or via an existing communication channel, if sending through the GUI isn't possible for some reason

Feedback button

For anything that isn't an acute problem — ideas, small inconsistencies, "this could be better" — use the feedback button in the interface (if enabled by your admin). Your submission is saved locally and automatically turned into a tracked issue on our side. Status flows back: if we close the topic on our end, you'll see that in the feedback widget under "My submissions".

If the feedback button is disabled on your instance, or you prefer the direct route: hello@vesana.org.

Which path, when?

Situation Path
Concrete bug we can't reproduce without context Send a support bundle
Quick question, idea, small inconsistency Feedback button or mail
Urgent problem on a production instance Send a support bundle + mail hello@vesana.org directly noting urgency
Pricing/license question hello@vesana.org (see License tiers)

What you can check yourself before sending a bundle

A support bundle answers a lot automatically — still, it's worth a quick look at the most obvious places first, often the cause is resolved locally faster:

Next