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
* Add a prefix for tags cache files
Use lambda function name as a prefix when creating tags cache files accessed by the forwarder.
This will allow to use the same S3 bucket to store cache files from different forwarderst push
* Update readme file to include a section about troubleshooting s3 triggers creation
* Update aws/logs_monitoring/README.md
Co-authored-by: Michel Daviot <michel@daviot.info>
* Add cache prefix on init
* Updat readme
* update comment
---------
Co-authored-by: Michel Daviot <michel@daviot.info>
Copy file name to clipboardExpand all lines: aws/logs_monitoring/README.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -138,6 +138,10 @@ If you can't install the Forwarder using the provided CloudFormation template, y
138
138
139
139
If you encounter issues upgrading to the latest version, check the Troubleshooting section.
140
140
141
+
### Upgrade an older version to +3.106.0
142
+
Starting version 3.106.0 Lambda function has been updated to add a prefix to cache filenames stored in the S3 bucket configured in `DD_S3_BUCKET_NAME`.
143
+
This allows to use the same bucket to store cache files from several functions.
144
+
141
145
### Upgrade an older version to +3.99.0
142
146
143
147
Since version 3.99.0 the Lambda function has been updated to require **Python 3.11**. If upgrading an older forwarder installation to +3.99.0 or above, ensure the AWS Lambda function is configured to use Python 3.11
@@ -204,6 +208,14 @@ If you still couldn't figure out, please create a ticket for [Datadog Support][1
204
208
### JSON-formatted logs are not appearing in Datadog
205
209
If your logs contain an attribute that Datadog parses as a timestamp, you need to make sure that the timestamp is both current and in the correct format. See [Log Date Remapper][24] to learn about which attributes are parsed as timestamps and how to make sure that the timestamp is valid.
206
210
211
+
### Issue creating S3 triggers
212
+
In case you encounter the following error when creating S3 triggers, we recommend considering following a fanout architecture proposed by AWS [in this article](https://aws.amazon.com/blogs/compute/fanout-s3-event-notifications-to-multiple-endpoints/)
213
+
214
+
```
215
+
An error occurred when creating the trigger: Configuration is ambiguously defined. Cannot have overlapping suffixes in two rules if the prefixes are overlapping for the same event type.
0 commit comments