content of page

Author: cswatt

content/en/data_streams/business_transaction_tracking.md

@@ -1,8 +1,38 @@
 ---
 title: Business Transaction Tracking
+description: Monitoring transaction processing with Data Streams Monitoring's Business Transaction Tracking
 ---
 
 {{< callout url=https://www.datadoghq.com/product-preview/business-transaction-tracking/
  btn_hidden="false" header="Join the Preview!">}}
 Transaction Tracking is in Preview. Use this form to submit your request today.
-{{< /callout >}}
+{{< /callout >}}
+
+_Supported by Java and .NET tracers_.
+
+Business Transaction Tracking monitors the complete processing of individual transactions across synchronous and asynchronous systems to help you meet SLAs and regulatory requirements.
+
+With DSM's transaction tracking, you can:
+- Monitor end-to-end latency of transactions from receipt to completion, across synchronous and asynchronous data streams processes
+- Detect SLO breaches, stuck transactions, and dropped transactions
+- Identify transactions breaching SLAs to notify and compensate customers
+- Generate transaction ID reports to meet regulatory requirements
+- Troubleshoot by inspecting example delayed, stuck, or dropped transaction IDs  
+in APM, logs, or internal databases  
+
+Data Streams Monitoring (DSM) extracts transaction IDs from HTTP request/response headers and Kafka produced/consumed message headers. When an individual transaction's ID is available in headers across all services with a checkpoint, DSM can follow the transaction across these services until its completion.
+
+## Create a transaction pipeline
+
+1. Navigate to [<span class="ui">Data Streams Monitoring > Transactions</span>][1].
+1. Select <span class="ui">Create Transaction Pipeline</span>.
+1. In the modal, define:
+   - <span class="ui">Pipeline Name</span>: A name for your pipeline
+   - Steps to track transactios across services. For each step, select a <span class="ui">Service</span>, an <span class="ui">Environment</span>, and an <span class="ui">Extractor Type</span>. Define a <span class="ui">Header Name</span>.
+   {{< img src="data_streams/btt-create-pipeline.png" alt="The Create Transaction Tracking Pipeline modal at step 1, Define. Fields include Pipeline Name and SLO Duration. Two steps are configured: a start step using the transaction-generator service with an HTTP Response Header extractor type, and an end step using the transaction-queuer service with an HTTP Request Header extractor type." style="width:100%;" >}}
+   Click <span class="ui">Save and Continue</span>.
+1. Verify your checkpoints. If any checkpoints require configuration, copy and paste the provided environment variables into your service deployment.
+   {{< img src="data_streams/btt-configure-verify.png" alt="The Configure and Verify Checkpoints modal at step 2. Two services are listed with Needs Configuration status: transaction-generator with a start checkpoint, and transaction-queuer with a queuer-in checkpoint. Each service displays a DD_DATA_STREAMS_TRANSACTION_EXTRACTORS environment variable to copy into the service deployment." style="width:100%;" >}}
+   Click <span class="ui">Done</span>.
+
+[1]: https://app.datadoghq.com/data-streams/transactions