# Observability & Tracing 

In this tab, the user can read several information about endpoints, such as call time, response time, status, HTTP method, the URL from which it was called. In case of an error, the user can view the error message and go to the recording containing the moment of the exception.

![](/files/jNeTdXhJAA6OmjHnq6Oi)

Trace has several endpoint filtering options: 

* Filtering the endpoints by successful state
* Filtering the endpoints by unsuccessful state
* Filtering the endpoints by names

![](/files/tDMKnYRsPA9ARmGFkGmD)

![](/files/zjXufVgBIore4ejdP4gH)

Clicking on a particular span opens the span info tab where the user can read information about it. The information differs depending on the endpoint status.

![](/files/38GzUalo2UMOPyZMn0Hr)

In span info in failed endpoints, in addition to the necessary information, the user can use the Show error details button to go to the tab containing detailed information about the error or directly go to the exception recording with the Flight Recording button.

![](/files/1cpWOywv0FBrgxaTmatP)

Then you can find out what went wrong with Flight Recording technology. Line by line, value by value to answer the question "Why".

![](/files/x6zi2YnFiaJcRmTB0GcC)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://revdebug.gitbook.io/revdebug/revdebug-features/observability-tracing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.