What's the best way to find out the reason for the 500 errors when filtering for status:error in the Live Search view?

When a trace with an error is selected from the Live Search view, a side panel opens. This panel contains an "Errors" tab. Clicking this tab displays the specific error message, type, and a full stack trace. This provides the most direct and detailed information about the root cause of the error, which is essential for debugging 500 errors. The span summary and service map provide contextual information but not the specific error details.

B. The span summary provides metadata like duration, host, and tags, but it does not contain the detailed error message or stack trace needed for debugging.

C. The service map shows dependencies and error propagation, which is useful for high-level analysis but does not reveal the specific reason for a single error instance.

1. Datadog Documentation, "Explore Traces". In the "Trace View" section, the documentation describes the side panel that appears when a trace is selected. It explicitly mentions the "Errors" tab for viewing "error messages, types, and stack traces". (Datadog APM > Traces > Explore Traces)

2. Datadog Documentation, "APM Terminology". Defines a span and its associated tags, which can include error.msg, error.stack, and error.type. The "Errors" tab in the UI is the dedicated view for these tags. (Datadog APM > Getting Started > APM Terminology)