> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/opsmx-1/opsmx-context-engine/additional-resources/previous-releases/isd-3.12/data-and-intelligence-module-autopilot/observability/overview-1.md).

# Overview

![](/files/8fgOoV5yqPtiOGFPhNsP)

Following are the key benefits of the observability feature:

* Identify and remove bottlenecks in all your pipelines through customizable Application and Delivery dashboards. Improve security by rapidly tracing the use of any artifact that has vulnerabilities or other issues. Share best practices and identify problem areas across your entire software delivery environment.
* Enable developers to monitor applications during and after deployment to production, with the ability to detect issues and request for rollback quickly to avoid disruptions.
* Get a high-level view of thousands of pipelines through a single-dashboard to ensure that it is operational feasible and receive diagnosis based on historical information.


---

# 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://docs.opsmx.com/opsmx-1/opsmx-context-engine/additional-resources/previous-releases/isd-3.12/data-and-intelligence-module-autopilot/observability/overview-1.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.