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
|`s3_encoding`|Name of the encoding extension to use for S3 objects. For example, `awslogs_encoding` to use AWS logs encoding extensions. When unspecified, falls back to CloudWatch subscription filter handling | Optional |
|`encoding_extension`|Required: The name of the encoding extension to load which will decode the data received through supported sources |
60
60
61
61
### Example Configuration
62
62
63
-
```yaml
64
-
receivers:
65
-
awslambda:
66
-
s3_encoding: awslogs_encoding
67
-
68
-
extensions:
69
-
awslogs_encoding:
70
-
format: vpcflow
71
-
vpcflow:
72
-
file_format: plain-text
73
-
74
-
exporters:
75
-
otlphttp:
76
-
endpoint: "https://my-backend:443"
77
-
78
-
service:
79
-
extensions:
80
-
- awslogs_encoding
81
-
pipelines:
82
-
logs:
83
-
receivers: [awslambda]
84
-
exporters: [otlphttp]
85
-
```
86
-
87
-
## Examples
88
63
89
64
### Example 1: VPC Flow Logs from S3
90
65
91
66
```yaml
92
67
receivers:
93
68
awslambda:
94
-
s3_encoding: awslogs_encoding
69
+
encoding_extension: awslogs_encoding
95
70
96
71
extensions:
97
72
awslogs_encoding:
@@ -112,14 +87,16 @@ service:
112
87
exporters: [otlphttp]
113
88
```
114
89
115
-
In this example, `awslambdareceiver` receives a notification when a new VPC flow log file is stored in an S3 bucket. The receiver fetches the log file from S3 and parses it using the `awslogs_encoding` extension with vpcflow format. The parsed logs are then sent to an OTLP listener using the `otlphttp` exporter.
90
+
In this example, the `awslambdareceiver` is expected to be triggered when a VPC flow log is created at S3 bucket.
91
+
The receiver retrieves the log file from S3 and decodes it using the `awslogs_encoding` extension with the vpcflow format.
92
+
Parsed logs are forwarded to an OTLP listener via the `otlphttp` exporter.
116
93
117
94
### Example 2: ELB Access Logs from S3
118
95
119
96
```yaml
120
97
receivers:
121
98
awslambda:
122
-
s3_encoding: awslogs_encoding
99
+
encoding_extension: awslogs_encoding
123
100
124
101
extensions:
125
102
awslogs_encoding:
@@ -140,32 +117,37 @@ service:
140
117
exporters: [otlphttp]
141
118
```
142
119
143
-
### Example 3: CloudWatch Logs Subscription
120
+
### Example 3: CloudWatch Logs mode
144
121
145
122
```yaml
146
123
receivers:
147
124
awslambda:
125
+
encoding_extension: awslogs_encoding
126
+
127
+
extensions:
128
+
awslogs_encoding:
129
+
format: cloudwatch
148
130
149
131
exporters:
150
132
otlphttp:
151
133
endpoint: "https://my-backend:443"
152
134
153
135
service:
136
+
extensions:
137
+
- awslogs_encoding
154
138
pipelines:
155
139
logs:
156
140
receivers: [awslambda]
157
141
exporters: [otlphttp]
158
142
```
159
143
160
-
In this example, `awslambdareceiver` is invoked by a CloudWatch Logs subscription filter.
161
-
`s3_encoding`configuration is omitted since it is not needed for CloudWatch Logs.
162
-
The receiver automatically parses the CloudWatch Logs data using the default `awslogs_encoding` extension with cloudwatch format.
163
-
No explicit encoding configuration is needed. The parsed logs are then sent to an OTLP listener using the `otlphttp` exporter.
144
+
In this example, `awslambdareceiver` is expected to be triggered by a CloudWatch Logs subscription filter.
145
+
The receiver retrieves the logs from the event payload and decodes them using the `awslogs_encoding` extension with the cloudwatch format.
164
146
165
147
## Supported Data Types
166
148
167
-
- **Logs** (Primary support)
168
-
- **Metrics** (Future consideration)
149
+
- **Logs**: Supported through S3 and CloudWatch Logs event sources
0 commit comments