Optional additionalA container for additional, undeclared properties. This is a holder for any undeclared properties as specified with the 'additionalProperties' keyword in the OAS document.
If set to true, logs that matched the quota filter and sent after the quota has been met are dropped; only logs that did not match the filter query continue through the pipeline.
The unique identifier for this component. Used to reference this component in other parts of the pipeline (for example, as the input to downstream components).
Optional ignoreIf true, the processor skips quota checks when partition fields are missing from the logs.
A Datadog search query used to determine which logs this processor targets.
A list of component IDs whose output is used as the input for this component.
The maximum amount of data or number of events allowed before the quota is enforced. Can be specified in bytes or events.
Name of the quota.
Optional overflowThe action to take when the quota is exceeded. Options:
drop: Drop the event.no_action: Let the event pass through.overflow_routing: Route to an overflow destination.Optional overridesA list of alternate quota rules that apply to specific sets of events, identified by matching field values. Each override can define a custom limit.
Optional partitionA list of fields used to segment log traffic for quota enforcement. Quotas are tracked independently by unique combinations of these field values.
The processor type. The value should always be quota.
Generated using TypeDoc
The Quota Processor measures logging traffic for logs that match a specified filter. When the configured daily quota is met, the processor can drop or alert.