> For the complete documentation index, see [llms.txt](https://docs.cloudassert.com/azure-stack-billing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudassert.com/azure-stack-billing/2011.4/installation/deployment/operations-and-monitoring.md).

# Operations and Monitoring

Add monitoring rules for the following components in your environment via monitoring tools like SCOM and associated Management Packs:

* Windows Servers
* SQL Server
* IIS Web Server (in API Machines)
* API End points
* Billing Agent Service

You may in addition add monitoring for:

* DB growth and/or the Disk(s) hosting Billing Database is monitored for performance and more importantly Available Free Space.
* Event logs for Error level entries - though, beware of many false positives here. Only add monitoring of specific events if you have seen helping identify issues.
* Down level source systems and dependencies like:
  * Microsoft Azure Stack (MAS) usage endpoint
  * Windows Azure Pack (WAP) usage endpoint
  * Active Directory and/or ADFS, if your environment depends on it

Having the operations team educated and routed with automated alerts is also essential to prevent failures and to enable faster recovery from any failures.


---

# 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.cloudassert.com/azure-stack-billing/2011.4/installation/deployment/operations-and-monitoring.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.