> 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/overview/monitoring-concepts/application-performance-management/performance-intelligence.md). # Performance Intelligence The ability to monitor and analyze events from yesterday, last week, or last month, within the same time frame or reference point, presents a noteworthy challenge. Achieving this requires a synchronized data series. IT-Conductor monitors the performance of services, applications, and IT infrastructure through a predefined and custom set of Key Performance Indicators (KPIs). These time dimensions not only support active service level management but also enable retrospective troubleshooting by facilitating correlation, comparisons, and historical snapshots. ### Performance Monitoring in SAP Landscapes In the context of monitoring the performance of SAP systems, IT-Conductor helps enhance performance management in the following areas: * End-user experience services can track specific sets of key performance indicators for a custom set of metrics, such as user, transactions, locations, dialog vs HTTP, etc. * Service discovery of application-aware components and relationships * Composite services assembled from other services and monitors * Easily configure target availability, response times, and notifications if the goals are not met. * Drill down into services to discover the root cause. Performance Monitoring also involves the measurement of performance against a customized set of key performance indicators (KPIs) over a period of time. This requires synchronized data series. However, response time is a misleading indicator of performance. To put it into perspective, a system may have a 0.5-second response time, but there may still be constant complaints from users with bad response times. The better way would be to create groups of transactions, by any combination of these attributes such as TCODE, USER, TASK TYPE, APP SERVER, USER TERMINAL, etc. They may represent business processes, such as Sales-Order-to-Cash, and service level objectives may be set up for average response times across orders (VA01, VA02, VA03), delivery (VL01N, VL02N, VL03N), shipping (VT01N, VT02N, VT03N), and billing (VF01, VF02, VF03). Then aggregate their KPIs where the default would still be dialog response time but it could be database response time, network GUI time, etc. Monitor and manage them automatically against service-level objectives and trigger actions based on policy-based exceptions such as alerts and notifications. All that along with other application, database, and system metrics as well as events so that correlation can be used if needed during performance analysis. There's a multitude of data to analyze. It would be difficult to diagnose when issues occur. In the context of troubleshooting, correlation plays a huge part in finding out the root cause of the problem. IT-Conductor makes it easier for you to associate this information through the expandable service grid levels. ![Figure 5: Expandable Service Grid Levels by Component](https://377464071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXhp08OmU8050PePmMgDt%2Fuploads%2FHnvlo9SY7wkjrzIdWcYz%2F2935619612?alt=media) --- # 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.itconductor.com/overview/monitoring-concepts/application-performance-management/performance-intelligence.md?ask=&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.