This blog explores structured logging techniques for HTTP requests, Kafka events, and concurrent processing in Java, Golang, and Python.

HaloDoc is a healthcare technology platform that offers telemedicine services, online pharmacy, and health information resources to users in Indonesia. Through its platform, HaloDoc aims to improve access to healthcare services, empower patients to take control of their health, and facilitate collaboration between healthcare providers. Developers can learn from HaloDoc's innovative use of technology to address healthcare challenges, leveraging telemedicine, artificial intelligence, and data analytics to enhance patient care and outcomes.

Halodoc

Debugging in microservices is challenging without structured logging. This post explores logging strategies for HTTP requests, Kafka events, and concurrency in Java, Golang, and Python. It addresses context loss in Java’s multi-threading by introducing MDCAwareCompletableFuture and MDCAwareExecutorService, ensuring traceability in concurrent systems. A structured logging approach with Request ID, Transaction ID, and Parent Transaction ID is recommended for better traceability and debugging efficiency.

Log Standardization

Introduction: Consistent and Traceable Logging

The Challenge: Tracing Complexity in Distributed Systems

Standardization of Logging Across Operations

Java Implementation: Code Patterns and Pseudocode

Golang & Python Implementation: Code Patterns and Pseudocode

<p>It sounds to me like otel distributed tracing model.
Request id-&gt;otel trace id
Transaction id -&gt; span id
Parent transaction id -&gt; parent span id</p>
