> For the complete documentation index, see [llms.txt](https://playbook.necdigitalstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://playbook.necdigitalstudio.com/capabilities/development/monitoring.md). # Monitoring We need to know how our applications are performing at all times. Even at a microsecond level, we track how our platforms are responding. The [DevOps team](/team/nec-digital-studio-team.md#devops-engineer) look for bottlenecks, where the system is trying to do too much at once, so we can proactively fix them. If we spot an increase in users, we can spin up a new server to take the load before anyone would notice an impact on the application. The application support and devops teams are constantly monitoring, checking alerts and then taking early action to fix potential issues. We’re focused on delivering full availability, so our users never have to log a call. For more information on how we support live products, [check out the live section of project delivery](/projects/the-structure-of-a-digital-project/live.md). --- # 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://playbook.necdigitalstudio.com/capabilities/development/monitoring.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.