Skip to content

Commit f42d7f2

Browse files
authored
Revert "docs: added new processing rule exclude_truncated to not ingest trunc…" (#30449)
This reverts commit 2199d1c.
1 parent 1688d15 commit f42d7f2

File tree

1 file changed

+0
-79
lines changed

1 file changed

+0
-79
lines changed

content/en/agent/logs/advanced_log_collection.md

Lines changed: 0 additions & 79 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,6 @@ After you set up [log collection][1], you can customize your collection configur
3131
- [Filter logs](#filter-logs)
3232
- [Exclude at match](#exclude-at-match)
3333
- [Include at match](#include-at-match)
34-
- [Exclude truncated](#exclude-truncated)
3534
- [Scrub sensitive data from your logs](#scrub-sensitive-data-from-your-logs)
3635
- [Multi-line aggregation](#manually-aggregate-multi-line-logs)
3736
- [Automatically aggregate multi-line logs](#automatically-aggregate-multi-line-logs)
@@ -270,84 +269,6 @@ spec:
270269
{{% /tab %}}
271270
{{< /tabs >}}
272271

273-
### Exclude truncated
274-
275-
| Parameter | Description |
276-
|---------------------|--------------------------------------------------------------------|
277-
| `exclude_truncated` | When present, it excludes truncated logs and does not send to Datadog. |
278-
279-
For example, to **filter out** truncated logs:
280-
281-
{{< tabs >}}
282-
{{% tab "Configuration file" %}}
283-
284-
```yaml
285-
logs:
286-
- type: file
287-
path: /my/test/file.log
288-
service: cardpayment
289-
source: java
290-
log_processing_rules:
291-
- type: exclude_truncated
292-
```
293-
294-
{{% /tab %}}
295-
{{% tab "Docker" %}}
296-
297-
In a Docker environment, use the label `com.datadoghq.ad.logs` on the container that is sending the logs you want to filter, to specify the `log_processing_rules`. For example:
298-
299-
```yaml
300-
labels:
301-
com.datadoghq.ad.logs: >-
302-
[{
303-
"source": "java",
304-
"service": "cardpayment",
305-
"log_processing_rules": [{
306-
"type": "exclude_truncated"
307-
}]
308-
}]
309-
```
310-
311-
**Note**: The label value must follow JSON syntax, which means you should not include any trailing commas or comments.
312-
313-
{{% /tab %}}
314-
{{% tab "Kubernetes" %}}
315-
316-
In a Kubernetes environment, use the pod annotation `ad.datadoghq.com` on your pod to specify the `log_processing_rules`. For example:
317-
318-
```yaml
319-
apiVersion: apps/v1
320-
metadata:
321-
name: cardpayment
322-
spec:
323-
selector:
324-
matchLabels:
325-
app: cardpayment
326-
template:
327-
metadata:
328-
annotations:
329-
ad.datadoghq.com/<CONTAINER_NAME>.logs: >-
330-
[{
331-
"source": "java",
332-
"service": "cardpayment",
333-
"log_processing_rules": [{
334-
"type": "exclude_truncated"
335-
}]
336-
}]
337-
labels:
338-
app: cardpayment
339-
name: cardpayment
340-
spec:
341-
containers:
342-
- name: '<CONTAINER_NAME>'
343-
image: cardpayment:latest
344-
```
345-
346-
**Note**: The annotation value must follow JSON syntax, which means you should not include any trailing commas or comments.
347-
348-
{{% /tab %}}
349-
{{< /tabs >}}
350-
351272
## Scrub sensitive data from your logs
352273

353274
If your logs contain sensitive information that need redacting, configure the Datadog Agent to scrub sensitive sequences by using the `log_processing_rules` parameter in your configuration file with the `mask_sequences` type.

0 commit comments

Comments
 (0)