You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `generate_metrics` processor creates custom metrics from logs.
75694
75697
Metrics can be counters, gauges, or distributions and optionally grouped by log fields.
75695
-
The generated metrics must be routed to a metrics destination using the input `<processor-id>.metrics`.
75698
+
75699
+
There must be a destination whose `inputs` reference this processor with the `<processor-id>.metrics` suffix to route the generated metrics. All destination types normally supported for `metrics` pipelines are also supported as metrics destinations in `logs` pipelines.
description: Compression configuration for HTTP requests.
76200
76205
properties:
@@ -77566,6 +77571,8 @@ components:
77566
77571
- `drop`: Drop the event.
77567
77572
- `no_action`: Let the event pass through.
77568
77573
- `overflow_routing`: Route to an overflow destination.
77574
+
77575
+
When `overflow_routing` is used, there must be a destination whose `inputs` reference this processor with the `<processor-id>.overflow_events` suffix to route the overflowing events. Only the following destination types support overflow inputs: `amazon_s3_generic`, `amazon_s3`, `google_cloud_storage`, and `azure_storage`.
0 commit comments