Overview

As your infrastructure and applications grow, so does your log volume and the complexity of the data. A large volume of logs can introduce a lot of noise and make it difficult to analyze and troubleshoot logs. Use Observability Pipelines’ processors to decide which logs are valuable and which ones are noisy and uninteresting, before sending your logs to their destinations. You can use the following processors in the Observability Pipeline Worker to manage your logs:

• Filter: Add a query to send only a subset of logs based on your conditions.
• Sample: Define a sampling rate to send only a subset of your logs.
• Quota: Enforce daily limits on either the volume of log data or the number of log events.
• Dedupe: Drop duplicate copies of your logs, for example, due to retries because of network issues.
• Remap: Add, drop, or rename a field in your logs.

Select a log source to get started:

• Datadog Agent
• Fluentd or Fluent Bit
• Google Pub/Sub
• HTTP Client
• HTTP Server
• Logstash
• Splunk HTTP Event Collector (HEC)
• Splunk Heavy or Universal Forwarders (TCP)
• Sumo Logic Hosted Collector
• rsyslog or syslog-ng

Further reading

Documentation, liens et articles supplémentaires utiles:

Strategies for Reducing Log VolumeDOCUMENTATION