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
{{ message }}
Repository navigation
Bug: Why does DataDogProvider add_metric forceset a timestamp #6961
we have been trying to send custom metrics with lambda powertools to datadog for a few days. While enhanced metrics were sent and received on Datadog, custom metrics did not show up.
After some debugging we found something peculiar in the DatadogProvider and would like to know if there is a reason behind the code and whether there are certain settings to be set to make it work.
The extension does not support timestamps for distributions so we create a
a thread stats writer to submit metrics with timestamps to the API
Running this on our end did not succeed in sending / receiving custom metrics. Creating a custom Provider which does not override the timestamp however, allowed it to succeed.
Are there some settings we are missing to be able to use the Thread Stats Writer or is this an unwanted behavior?
Hey @manzkel thanks a lot for your huge patience on this topic! I was testing exhaustively this problem and I'm not sure if I'm reproducing the error.. I'm using this those layers in my Lambda with Python 3.12:
I tried lot of times sending data both with timestamp and without timestamp and in both cases I was able to create custom metrics + enhanced metrics in DataDog
If it's still possible, can you help me understand a little better what's happening on your side?
This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Activity
leandrodamascena commentedon Jul 8, 2025
Hey @manzkel thanks a lot for your huge patience on this topic! I was testing exhaustively this problem and I'm not sure if I'm reproducing the error.. I'm using this those layers in my Lambda with Python 3.12:
I tried lot of times sending data both with timestamp and without timestamp and in both cases I was able to create custom metrics + enhanced metrics in DataDog
If it's still possible, can you help me understand a little better what's happening on your side?
I'm converting this discussion into an issue.
leandrodamascena commentedon Aug 11, 2025
Hi @manzkel, I'm closing this issue for now, but feel free to reopen it if you still have issues.
powertools-for-aws-oss-automation commentedon Aug 11, 2025
Warning
This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.