> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/dashboards/data-quality-dashboard.md).
# Data Quality Dashboard
The Data Quality Dashboard includes two reports that provide a visual overview for users to monitor data quality.
* **Service Desk Data Quality Trends:** This report tracks trends in data quality issues raised through service desk requests. It uses bar graphs to compare the number of service requests raised for data quality issues in a month against the number of requests resolved in that same month over a year.
* **Data Quality Rule (DQR) Performance:** These reports display the success and failure rates for each DQR dimension. This allows users to identify areas where data quality issues are most prevalent and prioritize improvement efforts. The reports use color-coded pie charts to visually represent the execution status of DQRs within each dimension (successful vs. failed).
---
# 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.ovaledge.com/release8.2/dashboards/data-quality-dashboard.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.