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 name of the source on which the triggering operation was performed
172
+
"myBucketName",
173
+
// The type of the operation that was performed on the data (usually "insert", "edit" or "delete")
174
+
"edit",
175
+
// The document name/table subjected to the operation
176
+
Some("/myFolder/myFile.txt"),
177
+
);
178
+
```
179
+
180
+
Even though DynamoDB is a data source, it's recommended to use a `pubsub` layer when processing DynamoDB Streams events.
181
+
182
+
### Timer layer
183
+
184
+
This layer could be used when the lambda is invoked periodically by the Amazon EventBridge Scheduler.
185
+
186
+
```rust
187
+
letcron_telemetry_layer=OtelLambdaLayer::timer(
188
+
provider,
189
+
// The schedule period as Cron Expression
190
+
Some("0/5 * * * ? *"),
191
+
);
192
+
```
193
+
194
+
### HTTP layer
195
+
196
+
Tracing for API Gateway events is not fully supported since that would require extracting tracking metadata from the event payload, but parsing event body is not supported by the `OtelLambdaLayer` implementation.
197
+
198
+
Though it's still possible to create a simple HTTP layer to set the correct trigger type:
0 commit comments