> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/feature-guides/data-management/metric-filtering.md).
# Metric Filtering
Filter metrics with Bindplane
Sources that collect metrics can be configured to filter out any number of metrics. When a metric is filtered out, it will not be sent to any destination.
## Configuration
Metric filtering can be configured for a source when initially creating it, or an existing source\
can be edited to change its filtering. Once saved, all collectors collecting that source will be updated to use the updated filter settings.
The controls for filtering metrics are found in the `Advanced` section of the source configuration form.\
Available metrics are organized in groups, allowing you to quickly enable or disable filtering for\
multiple related metrics. The checkbox next to each metric indicates whether it will be sent to destinations. That is, unchecking the box for a metric will filter it out.
In the above image, all metrics in the `Virtual Server` group will be filtered out, as well as `bigip.pool.availability` and `bigip.pool.packet.count`.
---
# 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.bindplane.com/feature-guides/data-management/metric-filtering.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.
