Structured Logs embrace the power of machine-readable logs HELIO MEDEIROS @helmedeiros 

Logging: The process of recording events during a computer program execution “ 

No content

No content

web.app { logs
 stream past present 

22:55:40 INFO Initializing hub 22:55:40 INFO Starting web server 22:55:42 INFO Incoming connection from 127.0.0.1:37843 22:55:42 DEBUG Connection upgraded 22:55:42 DEBUG Receive message: “ping” 

>>> logging 

log = logging.getLogger() log.info("Starting web server”) log.debug(“Actual memory: %s”, $mem) 

Structured logging: Logging events with specific fields (key= value) “ 

INFO[06-06|22:55:40] Incoming connection component= websocket.serveWs remote= 127.0.0.1:37843 event= connection.new INFO[06-06|22:55:40] Connection upgraded component= websocket.serveWs remote= 127.0.0.1:37843 event= connection.upgraded DEBUG[06-06|22:55:42] Receive message component= websocket.connection remote= 127.0.0.1:37843 event= message.new message= ping 

>>> logging structured 

>>> log = logging.getLogger() >>> log = log.bind( … user=“helio” … remote=“127.0.0.1:36509” … ) 

>>> log.info(“message.new”, message=“ping”) 22:55:42 DEBUG user=“helio” remote=“127.0.0.1:37843” event=“message.new” message=“ping” 

“Unstructured” logs suffer from two big problems 

1 It is difficult to parse 

2 Individual messages lack context 

{ “timestamp”: “Jun 6 15:33:06 +0000”, “app”: “web”, “message”: “Receive Message”, “event”: “message.new”, “ip”: “127.0.0.1”, “Trace-Id”: “48e276bd-cb52-4e12- abaf-2f0fcf746786” } 

correlation identifiers: Unique identifier that allow reference to particular transactions or event chains “ 

Structured Logs embrace the power of machine-readable logs HELIO MEDEIROS @helmedeiros