如何在Spring Cloud Sleuth中获取当前traceId？

Absolutely! Grabbing the current traceId with Spring Cloud Sleuth is totally doable, and fits perfectly with your use case—no need to expose it in API responses, just tuck it into alert emails for your dev team. Here are the two most reliable ways to do it:

1. Use the Tracer Bean (Recommended) #

Spring Cloud Sleuth auto-configures a Tracer bean in your application as long as you have the correct dependencies set up. This is the most robust method because it directly interacts with Sleuth's span context.

Here's how to use it in a service class that handles your alert logic:

import org.springframework.cloud.sleuth.Tracer;
import org.springframework.stereotype.Component;

@Component
public class AlertNotificationService {

    private final Tracer tracer;

    // Constructor injection (preferred over field injection)
    public AlertNotificationService(Tracer tracer) {
        this.tracer = tracer;
    }

    public void sendDevAlert(String alertDetails) {
        // Get the current traceId (with null safety)
        String currentTraceId = null;
        if (tracer.currentSpan() != null) {
            currentTraceId = tracer.currentSpan().context().traceId();
        }

        // Build your alert email with the traceId (if available)
        String emailContent = String.format("Alert: %s%nTrace ID for debugging: %s", 
                                           alertDetails, 
                                           currentTraceId != null ? currentTraceId : "No active trace");
        
        // Call your email sending logic here
        sendEmailToDevTeam(emailContent);
    }

    // Dummy method for illustration
    private void sendEmailToDevTeam(String content) {
        // Implementation goes here
    }
}

Key Note: Always add a null check for tracer.currentSpan()—if you're running code outside of an active request thread (like a scheduled task with no trace context), the span will be null.

2. Pull from SLF4J's MDC #

Sleuth automatically populates the SLF4J Mapped Diagnostic Context (MDC) with the traceId (and spanId) for every active request. This is a quick way to grab the traceId if you're already using logging in your application.

import org.slf4j.MDC;

public String getCurrentTraceIdFromMdc() {
    // Default key for traceId in Sleuth is "traceId" (lowercase)
    return MDC.get("traceId");
}

Heads Up: If you've customized Sleuth's MDC key names via configuration (e.g., spring.sleuth.mdc.trace-id-key), you'll need to use your custom key instead of the default "traceId". Also, MDC context doesn't automatically carry over to async threads—you'll need to use Sleuth's AsyncConfigurer wrapper if you're triggering alerts from async code.

Either method will work for your alert email use case. The Tracer bean approach is generally safer for edge cases, while the MDC method is more concise for simple request-bound scenarios.

内容的提问来源于stack exchange，提问作者Daniel Haughton