ausimian / loki_logger_handler / f2bb17b99f97ebe7482a64939252e4c3bc2bd8d5-PR-6

94%

main: 94%

Pull #6

github

fix: prevent a single bad event from removing the handler

A malformed log event could raise inside Formatter.format/3, which runs
inline in Handler.log/2. Erlang's logger removes a handler whose log/2
raises, so one bad event silently disabled Loki logging for the lifetime
of the node.

Wrap the format step in a rescue: on failure the handler buffers a
best-effort fallback entry (level label + inspected message) and emits a
[:loki_logger_handler, :format, :error] telemetry event instead of
letting the exception propagate. Also add catch-all clauses to
format_message/2, the format_report/2 report_cb case, and
extract_timestamp/1 so unexpected-but-recoverable shapes degrade
gracefully rather than raising.

Closes #2

13 of 13 new or added lines in 2 files covered. (100.0%)

295 of 313 relevant lines covered (94.25%)

29.67 hits per line