1d ago · 11 min read · Most .NET teams start logging the same way: they inject ILogger<T>, call _logger.LogInformation(...), and move on. Then the application grows. Incidents happen at 2 AM. Someone needs to find one speci
Join discussion
6d ago · 8 min read · Modern backend systems rarely run as a single application on a single server anymore. Today’s systems are distributed, run across multiple services, and operate in different regions and infrastructure
Join discussionMar 9 · 12 min read · TLDR: Fluentd is an open-source data collector that decouples log sources from destinations. It ingests logs from 100+ sources (Nginx, Docker, syslog), normalizes them to JSON, applies filters and transformations, and routes them to 100+ outputs (Ela...
Join discussionMar 7 · 4 min read · Originally published at orquesta.live/blog/full-audit-trail-ai-code-generation When AI writes your code, every step matters. Every decision made by the AI agent, every suggestion it generates, and every line of code it modifies can have profound imp...
Join discussionMar 3 · 8 min read · Observability for Developers: Logging, Metrics, and Tracing "Add more logging" is the default response when something breaks in production. But unstructured log lines piped to stdout are the least useful form of observability. Modern applications nee...
Join discussionMar 3 · 11 min read · Observability for Developers: Logs, Metrics, Traces, and OpenTelemetry Observability is the ability to understand what your system is doing from its external outputs. When something breaks in production -- and it will -- observability is the differen...
Join discussionMar 3 · 11 min read · Log Management Tools: ELK Stack, Loki, and Cloud Alternatives Logs are the most expensive part of most observability stacks. Not because the tools are expensive (though they can be), but because logs are verbose by nature. Every HTTP request, every d...
Join discussion
