Ce produit n'est pas pris en charge par le site Datadog que vous avez sélectionné. ().
Cette page n'est pas encore disponible en français, sa traduction est en cours. Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.
Disponible pour:
Logs|Metrics
Overview
This processor drops all logs or metrics (PREVIEW indicates an early access version of a major product or feature that you can opt into before its official release.Glossary) that do not match the specified filter query. If a log or metric is dropped, the data isn’t sent to any subsequent processors or destinations.
Setup
To set up the filter processor:
Define a filter query.
Logs or metrics that match the query are sent to the next component.
Logs or metrics that don’t match the query are dropped.
Filter query syntax
Each processor has a corresponding filter query in their fields. Processors only process logs or metrics that match their filter query.
The following are filter query examples:
NOT (status:debug): This filters for logs that do not have the status DEBUG.
status:ok service:flask-web-app: This filters for all logs with the status OK from your flask-web-app service.
This query can also be written as: status:ok AND service:flask-web-app.
host:COMP-A9JNGYK OR host:COMP-J58KAS: This filter query only matches logs from the labeled hosts.
user.status:inactive: This filters for logs with the status inactive nested under the user attribute.
http.status:[200 TO 299] or http.status:{300 TO 399}: These two filters represent the syntax to query a range for http.status. Ranges can be used across any attribute.
