After you've sent us your OpenTelemetry data and opened your service (entity) in the UI, click on Transactions to identify slow or error transactions that might be causing a spike in your application's response time. To get a list of transactions, go to the Transaction Summary page, and then select the transactions table.
New Relic's notion of a transaction encapsulates one logical unit of work in a software application - generally, this is work performed by a single process.
With OpenTelemetry, we rely on
SpanKind for mapping trace data to New Relic's concept of a transaction. A
consumer is used to identify the entry point of a process - that is, these are spans that are either root spans or child spans of a remote process.
For your data to appear in this section, make sure it has the following:
To learn about OpenTelemetry in other UI pages, see the UI overview.