Grouping and JSON log messages
See original GitHub issueWe’ve recently switched to a new logging format, which is in JSON instead of a simple string.
This has had a detrimental affect on our sentry captures, as it is unable to group the log messages by title. Instead, it looks like this:
The message we are sending looks like the following:
{"code": "INT33443",
"message": {
"message": "Error syncing your account",
"type": "public",
"company_id": 3
}
}
Is there a way I can get sentry to display message->message
as the title and group by that?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:7 (3 by maintainers)
Top Results From Across the Web
8 Essential Tips for JSON logging - Papertrail
8 Essential Tips for JSON logging · Validate Your JSON · Create a Standard Schema · Include a Timestamp in Every Message ·...
Read more >Structured logging - Google Cloud
Because JSON is more precise and versatile than text lines, you can use JSON objects to write multiline messages and add metadata. To...
Read more >Parse JSON Formatted Logs - Sumo Logic Docs
The JSON operator allows you to extract values from JSON logs with most JSONPath expressions. See the supported JSONPath syntax elements below.
Read more >JSON Logs with CloudWatch Logs Insights - In Plain English
Insights will automatically parse the content and create fields based on the JSON message. Insights can extract a maximum of 1000 log event ......
Read more >Group Logs - Datadog Docs
With pattern aggregation, logs that have a message with similar structures are grouped altogether. Optionally select one to three faceted fields to pre- ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
As @allan-simon mentioned, you can update the EventHandler and use a custom
logging.Formatter
.This works for me:
And used:
This issue is related to some other issues (I tagged all of them with the “Integration: Logging” label) I put it in the internal backlog with low priority. Any help here is greatly appreciated!