# Documentation

> Understand kbdiag, run your first check, and look up commands by problem.

---

LLMS index: [llms.txt](/kbdiag-docs/llms.txt)

---

## Start here

- [About kbdiag](about/): who it serves, where it runs, and what it will not do.
- [Capabilities](features/): the question each command answers.
- [First check](get-started/): build, install, connect, and read exit codes.
- [User manual](reference/): every command, flag and output field.

Start with `status` and `sessions`. If you already have a problem in front of you, pick a command from the capabilities page or follow a troubleshooting scenario.

[Troubleshooting: lock waits and long-running SQL](/kbdiag-docs/docs/scenarios/)

---

Section pages:

- [About kbdiag](/kbdiag-docs/docs/about/): Read-only command-line diagnostics for KingbaseES: a verdict, the evidence and the next step.
- [Capabilities](/kbdiag-docs/docs/features/): Choose a command by the question you need answered: instance, sessions, locks, transactions, waits, replication slots.
- [Your first check](/kbdiag-docs/docs/get-started/): Build the binary, install it on the database host, connect, and read the verdict and exit code.
- [Troubleshooting scenarios](/kbdiag-docs/docs/scenarios/): Move from a symptom to the evidence, then confirm the outcome.
- [User manual](/kbdiag-docs/docs/reference/)