Ce processeur filtre les logs qui correspondent à la requête de filtrage spécifiée et ignore tous les logs qui ne correspondent pas. Si un log est ignoré par ce processeur, aucun des processeurs inférieurs ne le reçoit. Ce processeur peut filtrer les logs inutiles, tels que les logs de débogage ou d’avertissement.

Pour configurer le processeur de filtre :

• Définissez une requête de filtre. La requête que vous spécifiez filtre et ne transmet que les logs qui lui correspondent, en laissant de côté tous les autres logs.

Filter query syntax

Each processor has a corresponding filter query in their fields. Processors only process logs that match their filter query. And for all processors except the filter processor, logs that do not match the query are sent to the next step of the pipeline. For the filter processor, logs that do not match the query are dropped.

For any attribute, tag, or key:value pair that is not a reserved attribute, your query must start with @. Conversely, to filter reserved attributes, you do not need to append @ in front of your filter query.

For example, to filter out and drop status:info logs, your filter can be set as NOT (status:info). To filter out and drop system-status:info, your filter must be set as NOT (@system-status:info).

Filter query examples:

• NOT (status:debug): This filters for only 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.

Learn more about writing filter queries in Datadog’s Log Search Syntax.