> For the complete documentation index, see [llms.txt](https://boxlang.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boxlang.ortusbooks.com/boxlang-+-++/modules/bx-mcp/reference/prompts/infrastructure-and-incident.md).

# Infrastructure & Incident

Pre-built prompts for web server diagnostics, route performance analysis, incident triage, error spike response, and post-incident review.

## Web Server & Routing

| Prompt                       | Description                                                                                                                           | Arguments                                                                     |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| `web_server_diagnostics`     | Deep-dive Undertow diagnostics: worker thread pool saturation, IO pool, active/queued requests, listener stats, WebSocket connections | —                                                                             |
| `slow_request_analysis`      | Identify slow inbound HTTP requests: correlates captured samples with per-route metrics to surface worst-performing endpoints         | `limit` *(optional, default: 50)*                                             |
| `route_performance_analysis` | Per-route HTTP performance: identify slowest and highest-traffic endpoints, error rates, prioritized optimization backlog             | `sortBy` *(optional, default: avgLatency)*, `limit` *(optional, default: 20)* |

## Incident Response

| Prompt                      | Description                                                                                                                     | Arguments                      |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ |
| `incident_triage`           | Rapid incident triage: scan errors, threads, memory, web server, datasources, and executors to identify what's broken right now | —                              |
| `error_spike_response`      | Error spike response: correlate timing, identify blast radius, and recommend containment actions                                | `keyword` *(optional)*         |
| `cascade_failure_diagnosis` | Cascade failure diagnosis: trace failure chains across subsystems (datasource timeout → thread saturation → request queuing)    | —                              |
| `rollback_decision`         | Rollback decision: structured go/no-go comparison of current state vs. deployment baseline                                      | `expectedModules` *(optional)* |
| `post_incident_review`      | Post-incident review: collect timeline, identify impact, determine root cause, and generate improvement actions                 | `keyword` *(optional)*         |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://boxlang.ortusbooks.com/boxlang-+-++/modules/bx-mcp/reference/prompts/infrastructure-and-incident.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.