> 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/user-guide/monitoring/sap/business-process.md). # Business Process Monitoring Business Process Monitoring refers to the proactive monitoring of an organization's core business processes, including business application logs and messages, business documents, dialog transactions, and background jobs. It also involves monitoring interfaces to ensure seamless data transfer between software components. Monitoring business processes in IT-Conductor allows users to manage the overall business process performance and identify bottlenecks through cross-system observation of the technical infrastructure and components required to run business processes. IT-Conductor also allows users to design, create, and manage business process hierarchies using the drag-and-drop [Business Process Composer](/user-guide/monitoring/sap/business-process/composer.md). This feature streamlines the process of mapping out complex workflows and simplifies the overall business process management. --- # 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/user-guide/monitoring/sap/business-process.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.