> For the complete documentation index, see [llms.txt](https://support.incidentlake.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidentlake.com/management/cmdb.md). # CMDB Register the services and systems you attach to incidents. The **CMDB** (under **Management**) is the catalog of configuration items your organization cares about — services, systems, and other pieces you want to attach to incidents. ## Why it matters When an incident lists affected configuration items, you can: * See which services are involved on the incident and on the Status board * Break down analytics by configuration item * Tie risks and SLAs to the same catalog If the catalog is empty, incidents cannot name what was affected in a consistent way. ## Typical work * Add a configuration item with a clear name the team already uses * Keep ownership and related information up to date * Review history when the map of services changes * Define SLAs or SLOs on an item when your organization tracks them here {% hint style="info" %} Use the same names people say in Slack. A catalog nobody recognizes will not get attached to incidents. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://support.incidentlake.com/management/cmdb.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.