search

grisp / dgram_logger

Generic datagram logger which sends to various UDP based logging infrastructure
Apache License 2.0
7 stars 1 forks source link

SASL logging creates broken influxdb formatting #1

Closed peerst closed 5 years ago

peerst commented 5 years ago

We are not handling the type of msg and meta that SASL logging (which also happens when there is no SASL included) does. Since this was the main reason to start this application (see SASL logs in grafana annotations via udp -> influxdb 

{meta,#{domain=>[otp,sasl],error_logger=>#{tag=>info_report,type=>progress},file=>"supervisor.erl",gl=><0.157.0>,line=>1419,logger_formatter=>#{title=>"PROGRESS REPORT"},mfa=>{supervisor,report_progress,2},pid=><0.159.0>,report_cb=>fun logger:format_otp_report/1,time=>1562950738028808}}
{msg,{report,#{label=>{supervisor,progress},report=>[{supervisor,{local,dgram_logger_sup}},{started,[{pid,<0.160.0>},{id,dgram_logger},{mfargs,{dgram_logger,start_link,[]}},{restart_type,permanent},{shutdown,5000},{child_type,worker}]}]}}}
=PROGRESS REPORT==== 12-Jul-2019::18:58:58.028808 ===
    supervisor: {local,dgram_logger_sup}
    started: [{pid,<0.160.0>},
              {id,dgram_logger},
              {mfargs,{dgram_logger,start_link,[]}},
              {restart_type,permanent},
              {shutdown,5000},
              {child_type,worker}]
peerst commented 5 years ago

Fixed by https://github.com/grisp/dgram_logger/commit/c46a0e9c7a07299a2b4c7864458464caa0e0a053