Skip to content
SHC Docs

shc support bundle

collect a support bundle into a local archive

Collect the estate’s diagnostics into a local tar.gz you can inspect and hand to support: a scoped telemetry dump, the state snapshot, the no-ref render of every in-scope deployment (secrets stay ref+vault:// pointers — plaintext is never produced), the certificate inventory (metadata, never keys), and the fabric/mesh diagnostic state (never private keys). Everything passes the scrub before it is written, and nothing is ever uploaded — you review and send it yourself. Scope with the global -t/-s/-e flags; an estate-wide bundle needs a platform admin. Requires the support_bundle entitlement (any paid tier, or the 30-day trial).

shc support bundle [flags]
shc support bundle
shc support bundle -t acme --since 48h
shc support bundle -s myblog --file ./myblog-diag.tar.gz
shc support bundle --quick
--file string write the archive here (default: ./shc-support-bundle-<utc>.tar.gz)
-h, --help help for bundle
--quick skip the telemetry store dump (state, render, certs and fabric only)
--since string telemetry time range, as a Go duration (default "24h")
--config stringArray extra YAML config file to layer on top of auto-discovered config; repeatable, later files win
-d, --debug enable debug mode (default: $SHC_DEBUG)
-e, --environment string environment name (default: $SHC_ENVIRONMENT)
--exclude string comma-separated dotted paths to drop
--fields string comma-separated columns/keys to show (and their order)
--filter string comma-separated dotted paths to keep (drops everything else)
-o, --output string output format: tty|text|json|yaml (default: $SHC_OUTPUT)
-s, --stack string stack name (default: $SHC_STACK)
-t, --tenant string tenant name (default: $SHC_TENANT)
-v, --verbose verbose output (default: $SHC_VERBOSE)