/AWS1/CL_CWOTELPIPELINECONF¶
Defines the configuration for a pipeline, including how data flows from sources through processors to destinations. The configuration is specified in YAML format and must include a valid pipeline definition with required source and sink components. This pipeline enables end-to-end telemetry data collection, transformation, and delivery while supporting optional processing steps and extensions for enhanced functionality.
The primary pipeline configuration section are:
-
Source: Defines where log data originates from (S3 buckets, CloudWatch Logs, third-party APIs). Each pipeline must have exactly one source.
-
Processors (optional): Transform, parse, and enrich log data as it flows through the pipeline. Processors are applied sequentially in the order they are defined.
-
Sink: Defines the destination where processed log data is sent. Each pipeline must have exactly one sink.
-
Extensions (optional): Provide additional functionality such as Amazon Web Services Secrets Manager integration for credential management.
For more details on each configuration section see CloudWatch pipelines User Guide. Additional comprehensive configuration examples can be found in the CreateTelemetryPipeline API docs.
CONSTRUCTOR¶
IMPORTING¶
Required arguments:¶
iv_body TYPE /AWS1/CWOTELPIPELINECONFBODY /AWS1/CWOTELPIPELINECONFBODY¶
The pipeline configuration body that defines the data processing rules and transformations.
Queryable Attributes¶
Body¶
The pipeline configuration body that defines the data processing rules and transformations.
Accessible with the following methods¶
| Method | Description |
|---|---|
GET_BODY() |
Getter for BODY, with configurable default |
ASK_BODY() |
Getter for BODY w/ exceptions if field has no value |
HAS_BODY() |
Determine if BODY has a value |