> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/administer-and-govern/rollout-and-operations/operational-oversight-and-support.md).

# Operational oversight and support

Use Monitoring, Requests and support ownership together to keep automated operations observable and actionable.

A dependable automated operation needs a clear answer to two questions: **how will we know something needs attention, and who owns the response?**

## Use the right signal

Different surfaces tell you different things:

* **Requests** show deliberate human handoffs in running Workflows;
* **Monitoring** shows execution history, traces and failures;
* **Alerts** can surface configured recurring execution conditions;
* operator feedback shows whether technically successful work was operationally correct.

Do not treat a successful runtime status as proof that the business outcome was correct.

## Define ownership before the exception happens

For each production capability, identify:

* a process owner for the business outcome;
* someone able to inspect and change the implementation;
* the route for access or infrastructure problems that need IT involvement;
* the criteria for pausing or changing the automation;
* how recurring issues are fed back into improvement work.

This is especially important as more of the routine path moves into background execution, because fewer people will naturally observe every run.


---

# 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://docs.lleverage.ai/administer-and-govern/rollout-and-operations/operational-oversight-and-support.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.