Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Lambda Log Forwarder docs troubleshooting - timestamps #700

Merged
merged 5 commits into from
Oct 26, 2023
Merged

Update Lambda Log Forwarder docs troubleshooting - timestamps #700

Changes from 3 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
a6435a5
troubleshooting log dates section
mirzanurkic-dd Oct 15, 2023
69e568f
phrasing
mirzanurkic-dd Oct 15, 2023
8f27ee7
log > logs
mirzanurkic-dd Oct 15, 2023
9ab2936
modify heading
mirzanurkic-dd Oct 26, 2023
52b5bef
better phrasing
mirzanurkic-dd Oct 26, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion aws/logs_monitoring/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -191,9 +191,11 @@ You can also add additional logging or code for deeper investigation. Find instr

Manually updating the `.zip` code of the Forwarder may cause conflicts with Cloudformation updates for Forwarder installations where the code is packaged in a Lambda layer (default installation choice from version `3.33.0`) and cause invocation errors. In this case, updating the stack through Cloudformation to the latest available twice in a row (first with `InstallAsLayer` set to `false`, and then to `true`) should solve the issue as it will remove any `.zip` remnants and install the latest layer available.


If you still couldn't figure out, please create a ticket for [Datadog Support][10] with a copy of debugging logs.

### JSON-formatted logs not appearing in Datadog
mirzanurkic-dd marked this conversation as resolved.
Show resolved Hide resolved
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. To learn more about which attributes are parsed as timestamps, and how to make sure that the timestamp is valid, visit the [Logs Processors > Log date remapper documentation][24].
mirzanurkic-dd marked this conversation as resolved.
Show resolved Hide resolved

## Contributing

We love pull requests. Here's a quick guide.
Expand Down Expand Up @@ -558,3 +560,4 @@ Additional helpful documentation, links, and articles:
[21]: https://docs.datadoghq.com/logs/processing/pipelines/
[22]: https://docs.datadoghq.com/agent/guide/private-link/
[23]: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/transform-aws-serverless.html
[24]: https://docs.datadoghq.com/logs/log_configuration/processors/?tab=ui#log-date-remapper