> 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/reporting/available-reports.md).

# Available Reports

IT-Conductor generates a wide variety of reports for the systems and resources monitored by IT-Conductor. These reports include KPI reports, Capacity reports, Month-end reports, Ad hoc reports, and Custom reports.

Some reports are system-dependent, meaning that they work and show information only from that specific system landscape. Other reports can be customized to show the overall system landscape with their related components.

### Systems where Reports are Available <a href="#systems-where-reports-are-available" id="systems-where-reports-are-available"></a>

* ABAP
* JAVA
* BOBJ
* HANA
* Oracle
* ASE DB
* DB2
* Linux OS
* Windows OS
* MsSql
* Sybase
* MaxDb

### Types of Available Reports <a href="#types-of-available-reports" id="types-of-available-reports"></a>

* KPI Health Monitoring Reports
* File System Growth Reports
* Availability Reports
* File System Usage Reports
* CPU Memory Utilization Reports
* Backup Summary Reports
* System Activity Reports
* Job Alerts Reports
* HANA Mini-checks Reports
* SAP Landscape/LMDB Report
* File System Capacity Reports
* System Performance Reports
* System Maintenance Mode Report
* System Alerts Report
* Change Request Report
* Control-M Shouts Report
* Default Threshold Report
* Prod/Non-Prod Password Reset Report


---

# 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/reporting/available-reports.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.