Best of LoggingSeptember 2025

  1. 1
    Article
    Avatar of tigrisTigris·36w

    How LogSeam Searches 500 Million Logs per second

    LogSeam demonstrates how to build a high-performance security data lakehouse that searches 500 million logs per second with 1.5 TB/s throughput while reducing costs by 40-80%. The architecture converts JSON logs to compressed Parquet files, achieving 100x storage reduction, and uses globally distributed object storage with elastic compute for sub-second query responses across continents.

  2. 2
    Article
    Avatar of thebluegroundengBlueground Engineering·34w

    A Software Engineer’s Guide to Observability

    A comprehensive guide to observability for engineering teams, covering the three pillars (logging, tracing, metrics) and their practical applications. Explains why observability has become critical in the era of distributed systems and AI-generated code, where complexity is increasing while domain expertise is becoming more distributed. The guide focuses on understanding when and why to use different observability tools rather than just how to configure them.

  3. 3
    Article
    Avatar of lnLaravel News·34w

    Debugging and Logging in Laravel Applications

    A comprehensive guide covering Laravel's built-in debugging and logging capabilities, including tools like Laravel Debugbar, Telescope, and Xdebug for development environments. The guide demonstrates how to implement Sentry for production error tracking, set up structured logging with Monolog, detect slow queries, and use custom tags for better error context and performance monitoring.

  4. 4
    Article
    Avatar of infoworldInfoWorld·34w

    Advanced debug logging techniques: A technical guide

    Debug logging is essential for maintaining high-performance applications across different architectures. Effective debug logging requires being selective about what to log, using structured formats like JSON, including contextual information such as correlation IDs, and implementing techniques like parameterized logging and rate limiting. Key practices include avoiding over-logging, never logging sensitive data, maintaining consistent formatting, and using centralized log management platforms. The guide covers specific tools for different languages (Winston for Node.js, structlog for Python, SLF4J for Java) and emphasizes the importance of correlation IDs for distributed tracing in microservice environments.