here you goThings I’ve made, read and saved — shared here.

Archive

9,608 entries: 53 from X, 8,925 from Pinboard, saved 1998 to 2026.

Browse by tag, site, author, folder or language

Tags

Sites

Authors

Folders

Languages

8 entries#logging ×

2025

Grepping logs remains terrible - Chronicae Novis Rebus

chronicles.mad-scientist.club

look at victorialogs as an alternative to #elasticsearch

VictoriaLogs, a high performance log database. It’s not your average generic indexer like ElasticSearch and its ilk, nor is it anything like a traditional relational database. It shows some resemblance to document stores, but only on the surface. It is specifically built for logs. Structured data is indexed and tokenized. Due to tokenization, the on-disk (and thus, in-memory) data is a lot smaller, and many queries are considerably cheaper, even if performing a full scan: rather than comparing arbitrary long strings, it will compare much smaller, bounded integer tokens in most cases.

2023

Structured Logging

Structured logging is a programming practice of implementing a consistent, predetermined message format for application logs that allows the logs to be treated as datasets, which makes them amenable to search, and analysis to gather insights about application behaviour and performance.

Most programming languages and frameworks have libraries that make it easy to do structured logging.

Common Structured Logging formats are JSON(line) and key=value separated by white-space.

Structured logging in Go with slog -- interesting thing I learnt from this library - "nested keys".

Tracing: structured logging, but better in every way | Andy Dote


logdyhq/logdy-core: Supercharge terminal logs with web browser UI and low-code. It's like jq, tail, less, grep and awk merged together and available in a clean UI.

notes#logging#structured-logging

2021

2019

2018

2017

2010