Update Lambda Log Forwarder docs troubleshooting - timestamps (#700)

* troubleshooting log dates section

* phrasing

* log > logs

* modify heading

Co-authored-by: May Lee <[email protected]>

* better phrasing

Co-authored-by: May Lee <[email protected]>

---------

Co-authored-by: May Lee <[email protected]>

aws/logs_monitoring/README.md

@@ -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 are not appearing in Datadog
+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.
+
 ## Contributing
 
 We love pull requests. Here's a quick guide.
@@ -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