fix: logging level does not reflect in datadog #2645
Merged
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.
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764
The PR Description
What's new in this PR?
Issues
Currently, we are not being able to see correct level of severity in Datadog dashboards for internal builds
Causes (Optional)
Datadog, does not inform about anomalies spikes automatically. Also, we can not categorize by error level, since now everything is debug and info.
Solutions
Use a similar approach that Kermit uses for their
Logcat
implementation.Testing
Test Coverage (Optional)
How to Test
See logs on datadog, and should see them with colorful statuses 🟥 🟨 🟦 for each logged messages.
Attachments (Optional)
Before:
After:
Insights autogenerated
PR Post Submission Checklist for internal contributors (Optional)
PR Post Merge Checklist for internal contributors
References
feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764
.