kurahi support
Prints the version, OS, state directory, integrity and service state, and writes a redacted diagnostics bundle to attach to a ticket.
kurahi supportkurahi support --no-bundlekurahi support --jsonkurahi support --id ops-bot --out ./ops-bot-support.tar.gzWhat the bundle contains
Section titled “What the bundle contains”<KOLO_HOME>/support/kolo-support-<timestamp>.tar.gz holds:
summary.json: version, OS, state directory, integrity gate result, service state and health.config.redacted.json: the config with every credential-looking value replaced.gateway-log.tail.txt: the last 400 gateway log lines, with credential-looking values replaced.
Secrets never enter the bundle. The bundle is written locally and leaves the machine only when you attach it to a ticket.
Options
Section titled “Options”--json: print the summary as JSON.--out <file>: bundle path (default shown above).--id <id>: service identity to report on. Without it the identity comes from the state root:KOLO_SERVICE_IDwhen set by the service environment, else the id recorded bykurahi service installin<KOLO_HOME>/service/service.json, else the default agent written bykurahi init, elsedefault.--no-bundle: print the summary only; write nothing.--lang <code>: message language,enorja.
Where to send it
Section titled “Where to send it”- Support: support@kodasoken.com
- Issues: https://github.com/koda-tokyo/kurahi/issues
- Vulnerabilities: security@kodasoken.com, never a public issue.
Exit codes
Section titled “Exit codes”- 0: summary printed (and bundle written unless
--no-bundle). - 1: the bundle could not be written.