Open-Source Observability · dromara

TLog

TLog is a lightweight distributed log tracking framework for Java microservices that automatically tags logs to enable service-to-service tracing. It integrates with popular logging frameworks (log4j, log4j2, logback) and RPC frameworks (Dubbo, Dubbox, Spring Cloud) with minimal code changes.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/dromara/TLog

601

GitHub stars

118

Forks

Java

Primary language

MIT

License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

Field	Value
Repository	dromara/TLog
Owner	dromara
Primary language	Java
License	MIT — OSI-approved
Stars	601
Forks	118
Open issues	23
Latest release	Unknown
Last updated	2026-03-30
Source	https://github.com/dromara/TLog

What TLog is

TLog provides distributed tracing via log tagging with three integration modes: JavaAgent (non-intrusive), bytecode injection (single-line), and configuration-based. It supports common logging and RPC frameworks, async threads, and task schedulers (Quartz, XXL-JOB) with reported performance overhead of ~0.01%.

Quickstart

Get the TLog source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/dromara/TLog.git2cd TLog3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Spring Cloud microservices requiring end-to-end log correlation

Teams running Spring Cloud deployments can enable automatic request tracing across service boundaries without modifying business code using the JavaAgent approach.

Dubbo/Dubbox RPC tracing with minimal instrumentation

Projects using Dubbo or Dubbox as their RPC layer can gain distributed tracing by leveraging TLog's built-in Dubbo adapter with configuration-based setup.

Async and task-based workflows in Java backends

Systems using thread pools, Quartz, or XXL-JOB can maintain trace context across async boundaries to correlate logs from scheduled or queued tasks.

Implementation considerations

Choose integration mode carefully: JavaAgent is zero-code but requires JVM startup flag; bytecode injection is single-line but adds compile-time overhead; config-based is most explicit but requires manual setup in each service.
Verify compatibility with your exact versions of log4j/log4j2/logback and RPC framework (Dubbo, Spring Cloud, etc.) before production adoption, as framework versions are not specified in available documentation.
Plan for async thread context propagation: TLog supports async scenarios but requires careful configuration; test multi-level async thread scenarios in your workload.
Monitor the reported 0.01% performance overhead claim: run load tests in your environment; actual overhead may vary by log volume and thread pool size.
Tag template customization should be planned upfront; changing templates in production may require log parsing adjustments.

When to avoid it — and what to weigh

Non-Java tech stack or polyglot services — TLog is Java-only. Heterogeneous architectures mixing Python, Node.js, Go, or other languages will require alternative tracing solutions (e.g., Jaeger, OpenTelemetry).
Need for strong vendor support or commercial SLA — This is a community-driven open-source project with no formal commercial support, release guarantee, or SLA. Organizations requiring guaranteed response times should evaluate enterprise alternatives.
Requirement for metrics and latency visualization — TLog focuses on log tagging and correlation, not metric collection or visual tracing dashboards. Projects needing APM-style performance insights should combine with Prometheus or a dedicated APM tool.
Large-scale production with frequent upstream changes — No formal release process or versioning strategy is documented. Projects in rapid evolution may face compatibility risks without clear release notes.

License & commercial use

MIT License. Permits commercial use, modification, and distribution with attribution; no patent grants or explicit liability disclaimers beyond standard MIT terms. Standard permissive OSI license.

MIT License permits commercial use. However, no formal support, indemnification, or liability limitation beyond the license is documented. Organizations requiring commercial guarantees should evaluate support agreements separately or consider enterprise APM vendors.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

Signal	Assessment
Maintenance	Moderate
Documentation	Adequate
License clarity	Clear
Deployment complexity	Low
DEV.co fit	Good
Assessment confidence	Medium

Security considerations

TLog injects trace tags into logs; ensure sensitive data (credentials, PII) is not inadvertently captured in tags or log content. JavaAgent and bytecode injection mechanisms should be reviewed in your security model to confirm acceptable. No security audit, CVE history, or vulnerability disclosure process is documented. Dependency security (third-party libraries) requires independent review.

Alternatives to consider

OpenTelemetry + Jaeger

Industry-standard, vendor-neutral distributed tracing with full metrics/traces/logs correlation, multi-language support, and active CNCF governance. Higher setup complexity but greater ecosystem integration.

Sleuth (Spring Cloud Sleuth)

Native Spring Cloud integration with distributed tracing; integrates with Zipkin/Jaeger backend. Requires Spring ecosystem; less lightweight but tighter framework coupling.

SkyWalking

Java-focused APM with low-overhead instrumentation, metrics, and visual dashboards. More feature-rich than TLog but larger deployment footprint; stronger maintenance posture.

Software development agency

Build on TLog with DEV.co software developers

TLog offers lightweight tagging-based tracing for Java microservices. Start with the JavaAgent approach for zero-code setup, or review alternatives like OpenTelemetry for broader language support. Contact our team for architecture review.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

tslog superlog zerolog

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source Observability API Development Cloud Deployment DevOps Talk to DEV.co

TLog FAQ

Does TLog require a separate backend or tracing server?

No. TLog operates purely as a log tagging library; it injects correlation IDs into logs. You manage centralized logs with your existing log aggregation stack (ELK, Splunk, etc.).

Can I use TLog with non-Spring Java frameworks?

TLog supports log4j/log4j2/logback and Dubbo/Dubbox/Spring Cloud RPC. Non-Spring frameworks using these logging/RPC layers may work, but compatibility is not explicitly documented beyond those frameworks.

What is the performance impact?

README claims ~0.01% overhead post load-testing. However, this claim is not independently verified. Test in your own environment with realistic log volume and async patterns before production.

Is there a commercial support option?

Not documented. The project is community-driven; support is via community groups and GitHub issues. Commercial SLA or vendor support is Unknown.

Software development & web development with DEV.co

Need help beyond evaluating TLog? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and open-source observability integrations — and maintain them long-term.

Ready to implement distributed log tracing?

Talk to DEV.co Schedule a Consultation