Merge pull request #5804 from alanwest/patch-1

Describe transactions in the context of OpenTelemetry

src/content/docs/more-integrations/open-source-telemetry-integrations/opentelemetry/view-your-opentelemetry-data-new-relic.mdx

@@ -289,6 +289,10 @@ For selected OpenTelemetry languages, you can see information about your metrics
 
 Use **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: From the **Transaction Summary** page, select the transactions table.
 
+New Relic's notion of a [transaction](https://docs.newrelic.com/docs/apm/transactions/intro-transactions/transactions-new-relic-apm#txn-defined) 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`](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#spankind) for mapping trace data to New Relic's concept of a transaction. A `SpanKind` of `server` or `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:
 
 <table>