Generate an offline support report

The report is generated from the running Gateway’s point-in-time state, makes no Keystone connection, and is written to standard output—not reports.directory in V1.

umask 077
/opt/particle_horizon/keystone-gateway report --endpoint http://127.0.0.1:8080 --format json > gateway-report.json

For HTTPS mTLS, add --ca-file, --cert-file, and --key-file. Add --include-leases only when support requests installation and lease identities; it requires an operator identity. Validate success from the zero exit code and valid JSON. Store/transfer the resulting file through approved customer controls and retain it only as long as needed. Reports omit signatures, private keys, state keys, tokens, principals, and idempotency keys, but detailed reports can contain customer instance identities. Reports are allowlisted state projections and do not include Gateway logs; collect logs separately and inspect them for credentials before sharing. Do not include credentials in command-line arguments or endpoint URLs, and review any error printed to stderr before forwarding it.