chore: Refactor logging format for Datadog pipeline integration #344
Conversation
This file contains 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
Coverage report
This PR does not seem to contain any modification to coverable code. |
ilee2u
force-pushed
the
ilee2u/log-format
branch
from
ba2bfad to
898e3d7
Compare
alangsto
approved these changes
Dec 19, 2024
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.
JIRA: Link to JIRA ticket
Description: This PR modifies the logging configuration to align with the Datadog Python pipeline standards.
Adjusting logging format to ensure they are compatible with Datadog’s ingestion requirements.
Sets Django request logs to the INFO level to maintain optimal log verbosity and clarity.
Merge checklist:
Post merge: