Post details
A colorful slog handler
A colorful slog handler
Learn 9 best practices for formatting your logs in production to make them easy to read, parse, and troubleshoot.
https://snarfed.org/matrix.webp https://snarfed.org/matrix.webp A long time ago, I decided to show Bridgy‘s end users its raw logs. Like, raw logs. HTTP requests, database reads and writes, JSON …
Command to get a sample of AWS ELB logs into a local sqlite database for ad-hoc analysis - GitHub - artyom/alblogs: Command to get a sample of AWS ELB logs into a local sqlite database for ad-hoc a...
Ed Welch joins Mat and Jon to discuss logging. They explore the different options for logging in Go, and discuss what data is worth including. Everything from log levels, formats, non-structured vs structured logs, along with common gotchas and good practices when dealing with logs at scale.
I don't think you should be logging that? 😳 (12 mins read).
Common pitfalls and dangerous things that you should be watching out for in your log messages.
Use SLF4J, not Log4J, as Your Logging Interface (3 mins read).
Why we should be using the interface API for logging, rather than the underlying implementation's API.
Auditing with Spring Boot Actuator (9 mins read).
How to use Spring Boot Actuator for your audit and business event logging needs.
Very interesting read, I can empathise with being the "logs person" 😂
Setting up fluentd to Parse Nested JSON from Docker (2 mins read).
How to configure fluentd to parse the inner JSON from a log message as JSON, for use with structured logging.
Migrating Your Spring Boot Application to use Structured Logging (6 mins read).
How to make your Spring Boot services more supportable by migrating to JSON-emitting structured logging.
This is an interesting post, and is an important one to think about. We need to remember that although now we've got lax data privacy / retention laws, it's only going to get more user-focused and protect everyone more (which is universally a good thing!) but that we need to make sure we're architecting things in the right way to handle this.
Also, while you're thinking about this - have a read through some production logs and wonder "what could a bad actor do with these? Could they phish a customer? Could they steal their identity? Or are these so useless that we may as well not be logging anything at all?"
You're currently viewing page 1 of 1, of 25 posts.