Datadog - missing message field for errors

[gorkunov]

We use logger_json for datadog integration.
When exception is logged using logger_json middlewares - it looks odd in datadog. Instead of readable message (e.g. exception message) - it shows raw json structure with the full payload. It seems that happens because for exceptions message key in payload not in the right place.
We tried a simple fix on a fork and it's working without issues.

prosapient@1307b95

[AndrewDryga]

@gorkunov does it also work for you if you leave the top-level message empty? Is there any processing rules on your DataDog that might break it? Having message in there is what the spec requires: https://docs.datadoghq.com/standard-attributes/?search=error.message

[gorkunov]

We didn't try empty message. But previously we used our own lib for logs with this formatter that was specially polished for exceptions: https://github.com/prosapient/statham_logger/blob/main/lib/datadog_formatter.ex.
As you can see we keep message on both levels + use field kind for errors.

[gorkunov]

You can find more details about fields here: https://docs.datadoghq.com/error_tracking/backend/logs?tab=serilog

[gorkunov]

Potentially problem with that formatting in datadog is missing field kind.

[Zanius]

We are also having this exact issue and have to rollback to a previous version.

[AndrewDryga]

@gorkunov @Zanius I've added message and kind to error structs (use the master branch), please give it a try and LMK if that doesn't solve the issue for you.

[gorkunov]

looks good now!