> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/inventory/how-to-solve-common-inventory-use-cases-with-filters.md).

# How to: Solve Common Inventory Use Cases with Filters

Filters turn the Inventory from a list into answers. This guide works through one common use case end to end; the same pattern applies to most cleanup and governance questions.

### Use case: find unhealthy new reports in production

Surface newly created Power BI reports in production that are unhealthy, excluding test artifacts, so they can be fixed before they impact business users.

**Why it matters.** New reports have had less time for validation, which makes early-life issues more likely: configuration gaps, performance inefficiencies, or incomplete modelling. Left unnoticed, unhealthy production reports degrade the user experience, increase refresh and capacity pressure, create downstream reliability issues, and reduce trust in production reporting. Reviewing them regularly lets your team intervene early.

**Who owns it.** Typically BI administrators, analytics platform owners, and data governance or Center of Excellence teams: the roles responsible for production health and standards.

**Steps:**

1. Open Control Tower and navigate to the team that contains your production Power BI workspaces.
2. Select **Inventory** to view all assets in scope.
3. Click **Filters** next to the search bar to open the Asset Filters panel.
4. Add rules that exclude assets whose name contains test, dev, or uat, grouped with **OR** so any match is excluded. If valid production assets contain these strings (for example, "evaluation" contains "uat"), add a rule or group to explicitly include them.
5. Give the filter a descriptive name (for example, production reports), click **Save**, then **Apply**.
6. Open the **Reports** tab and use the attribute filter to show only **Unhealthy** assets. Sort by creation date to focus on the newest ones first.


---

# 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:

```
GET https://docs.datalogz.io/guides/inventory/how-to-solve-common-inventory-use-cases-with-filters.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.