Your web service has some 500 Internal Server Error showing up on the trace explorer page. How do you drill down and find

When you click on a span in the Trace Explorer, it opens the detailed Trace View panel. This view contains a flame graph of the entire trace and several tabs for deeper analysis. The "Errors" tab is specifically designed to aggregate all errors that occurred within that trace, displaying the error type, message, and a full stack trace. This is the most direct and comprehensive way to investigate the root cause of a specific error.

C. The span summary (or Metadata tab) shows tags and metadata, which might include an error flag, but the full message and stack trace are in the Errors tab.

D. The service map provides a high-level view of dependencies and health metrics, not the specific error message for an individual trace.

E. The service page aggregates data for the entire service. While it has an error section, it does not drill down to the specific error instance you selected.

1. Datadog Documentation, "Explore Traces". This page describes the user interface for trace investigation, showing that clicking a span opens the Trace View. Screenshots and descriptions highlight the "Errors" tab as the location for error messages and stack traces. (See section: "Trace View").