> For the complete documentation index, see [llms.txt](https://support.incidents.cloud.solarwinds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidents.cloud.solarwinds.com/~/changes/lGFY3mJPy207GveiFTeX/incidents-page.md).

# Incidents Page

- [Incidents Details](https://support.incidents.cloud.solarwinds.com/~/changes/lGFY3mJPy207GveiFTeX/incidents-page/incidents-details.md): Get more details of an incident
- [Incident Activity Timeline](https://support.incidents.cloud.solarwinds.com/~/changes/lGFY3mJPy207GveiFTeX/incidents-page/incident-activity-timeline.md): View the Activity Timelines of an Incident
- [Communication Channels](https://support.incidents.cloud.solarwinds.com/~/changes/lGFY3mJPy207GveiFTeX/incidents-page/communication-channels.md): Enhance incident management communication - Add video calls, chatops, and external links to incidents. Create dedicated Slack Channels for seamless collaboration.
- [Create Incident Manually](https://support.incidents.cloud.solarwinds.com/~/changes/lGFY3mJPy207GveiFTeX/incidents-page/create-incident-manually.md): Tigger incidents manually
- [Incident Notes](https://support.incidents.cloud.solarwinds.com/~/changes/lGFY3mJPy207GveiFTeX/incidents-page/incident-notes.md): Share notes and collaborate with your team during incident resolution
- [Incident Watchers](https://support.incidents.cloud.solarwinds.com/~/changes/lGFY3mJPy207GveiFTeX/incidents-page/incident-watchers.md): Add watchers to your incident, allowing them to be notified about all the updates to that incident.
- [Past Incidents](https://support.incidents.cloud.solarwinds.com/~/changes/lGFY3mJPy207GveiFTeX/incidents-page/past-incidents.md): View similar incidents from the past to gain insights and shorten incident resolution time.


---

# 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.incidents.cloud.solarwinds.com/~/changes/lGFY3mJPy207GveiFTeX/incidents-page.md?ask=<question>&goal=<endgoal>
```

`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.