-
Notifications
You must be signed in to change notification settings - Fork 13
Insights: DataDog/datadog-lambda-extension
Overview
-
- 4 Merged pull requests
- 5 Open pull requests
- 2 Closed issues
- 0 New issues
Could not load contribution data
Please try again later
4 Pull requests merged by 3 people
-
chore(github): separate vulnerability scans
#739 merged
Jul 14, 2025 -
chore: Use rust-license-tool for license file
#741 merged
Jul 14, 2025 -
chore: Add workflow_dispatch trigger for rs_ci.yml
#742 merged
Jul 14, 2025 -
feat: Add jemalloc
#736 merged
Jul 10, 2025
5 Pull requests opened by 4 people
-
feat: Handle API key resolution failure
#732 opened
Jul 7, 2025 -
chore:add gitlab task to deploy to sandbox us-west-2 for e2e test
#733 opened
Jul 8, 2025 -
feat: dual shipping APM support
#735 opened
Jul 9, 2025 -
feat(apm): aggregate and flush data accordingly for DSM, Profiling, LLMObs, and Live Debugger
#737 opened
Jul 10, 2025 -
chore: Add doc and rename function for flushing strategy
#740 opened
Jul 11, 2025
2 Issues closed by 2 people
-
Datadog next gen keeps the lambda alive waiting for DogStatsD events
#726 closed
Jul 14, 2025 -
timeout when using datadog lambda-extension v82 python 3.12 container-based
#738 closed
Jul 11, 2025
4 Unresolved conversations
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
feat: Lazily resolve api key
#717 commented on
Jul 14, 2025 • 5 new comments -
"Error deserializing trace from request body" errors
#677 commented on
Jul 9, 2025 • 0 new comments -
Regularly failing dotnet install
#734 commented on
Jul 9, 2025 • 0 new comments -
wip: support asm
#695 commented on
Jul 9, 2025 • 0 new comments