fix: use tracing for all logs in datadog-serverless-compat #33
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nhulston
approved these changes
Aug 25, 2025
duncanpharvey
deleted the
duncan-harvey/datadog-serverless-compat-tracing
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Updates
datadog-serverless-compatto only usetracinglibrary for logging.Motivation
Multiple logging libraries were being used with different configurations,
logandtracing, which resulted in logs with different formats depending on where the log messages were being logged from.Additional Notes
Before change
After change
Describe how to test/QA your changes
Deployed to Azure Functions on all plans and verified logs are sent with the correct format.