After you've sent us your OpenTelemetry data and opened your service (entity) in the UI, click Databases to learn about the performance of the database queries your service is making. You can see which database calls (e.g.,
SELECT operation on the
ads table) are taking the most time in total or on average, or have the most throughput. Then you can investigate performance of an individual call and find traces that involve it.
With OpenTelemetry, spans have a
SpanKind=CLIENT describes a span that represents a call to a remote service, like a database. We use
SpanKind=CLIENT paired with the presence of the
db.system attribute to identify spans representing a call to a database.
For your OpenTelemetry data to appear in the Databases page, make sure it has the following attributes, in accordance with the OTel semantic conventions:
Top database calls
Top databases (by query time)
Top databases (by throughput)
To learn about OpenTelemetry in other UI pages, see the UI overview.