> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/overview/monitoring-concepts.md).
# Monitoring Concepts
### Background
Monitoring SAP systems can be labor-intensive and time-consuming, especially when managing different applications across varying platforms. Ensuring high availability, maintaining CPU and memory utilization at a certain threshold, and making sure processes are running without a miss, are just a few of the many other things you need to keep an eye on. Without monitoring tools, it would be extremely difficult to monitor the bits and pieces encompassing your entire SAP system landscape.
Application Performance Management (APM) tools allow the monitoring and managing of both the performance and availability of software applications. It also provides an effective and continuous insight into application health. In the context of meeting the service level agreement, it would be highly beneficial for organizations to relate several business processes, software, and infrastructure layers and continuously process large volumes and velocity of metric and event data on one platform.
IT-Conductor as a Software-as-a-Service APM tool goes beyond a platform and offers remote managed services, allowing customers to benefit from automatic monitoring templates to customized management requirements delivered at cloud speed. The solution focuses on service-level management, monitoring, automation, and performance intelligence. It also uses an advanced troubleshooting context synchronized with service health components to assist root cause analysis. IT-Conductor service templates simplify the correlation between complex application components and how they relate and impact overall performance and availability. This method has proven effective in analysis time, enhancing the overall service quality.
### Threshold and Overrides
IT-Conductor Monitoring is built around two concepts: Threshold and Override.
#### **Threshold**
Threshold is the definition of WHAT to monitor: an object (or multiple objects) and the object attributes containing the monitored value. They are automatically generated by IT-Conductor, based on templates, when you create an SAP instance. Customers with requisite permissions can create additional thresholds on the fly. For complex scenarios, you can always reach out and ask for assistance from ITC Support.
#### **Override**
Override is the definition of HOW to monitor: the threshold values used to trigger status change and alert generation. The override includes search criteria used to match with a specific monitored object. When a threshold tries to determine what values to use, it selects a single override in which the most precise criteria match the monitored object (based on how close the criteria class is to the monitored object class and the size of the criteria). The end users create the overrides for the existing thresholds.
See [Creating Threshold Overrides](/~/changes/j1RdUn49WBcajmJEmXUf/users-guide/notifications/creating-threshold-overrides.md) for more details.
### Alerts and Notifications
---
# 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.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/overview/monitoring-concepts.md?ask=&goal=
```
`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.