Nested Pipelines are pipelines within a pipeline. Use Nested Pipelines to split the processing into two steps. For example, first use a high-level filtering such as team and then a second level of filtering based on the integration, service, or any other tag or attribute.

A pipeline can contain Nested Pipelines and Processors whereas a Nested Pipeline can only contain Processors.

Hierarchy

  • LogsPipelineProcessor

Constructors

Properties

additionalProperties?: {
    [key: string]: any;
}

A container for additional, undeclared properties. This is a holder for any undeclared properties as specified with the 'additionalProperties' keyword in the OAS document.

Type declaration

  • [key: string]: any
filter?: LogsFilter

Filter for logs.

isEnabled?: boolean

Whether or not the processor is enabled.

name?: string

Name of the processor.

processors?: LogsProcessor[]

Ordered list of processors in this pipeline.

Type of logs pipeline processor.

Generated using TypeDoc