Debug package

When you hit an issue Scrydon support needs to investigate, you can download a debug package — a single .zip capturing your deployment's versions, service health, non-secret configuration, and recent logs.

Download it

1. Go to Settings → Organization → License (organization-admin only).
2. Click Download debug package.
3. A .zip named scrydon-debug-<org>-<timestamp>.zip downloads.
4. Review the contents (see below), then send it to your Scrydon contact.

What's inside

• system.json — platform/chart version, commit, build date, allowlisted env.
• license.json — your license tier, entitlements, and dates (never the signed token).
• policies.json, integrations.json, data-sources.json, storage.json — non-secret configuration state.
• health/*.json — reachability of each internal service.
• logs/*.log — recent application logs.
• manifest.json / README.txt — bundle metadata (including an errors list of any data that could not be collected) and a description.

What's excluded

Credentials are never read when building the package — API keys, database passwords, and signing secrets live in the secret store, which the package does not access, so they are excluded by design. Logs are additionally scrubbed for common secret shapes on a best-effort basis.

Logs can still contain data specific to your environment. Review the .zip before sending if your deployment may log sensitive information.