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 sync (like HTTP request/response) and async (like 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 Data Streams Monitoring > Transactions. You must complete the form to access this page.
2. Select Create Transaction Pipeline.
3. In the modal, define:
   • Pipeline Name: A name for your pipeline
   • Steps to track transactios across services. For each step, select a Service, an Environment, and an Extractor Type. Define a Header Name.

4. Click Save and Continue.
5. Verify your checkpoints. If any checkpoints require configuration, copy and paste the provided environment variables into your service deployment.

6. Click Done.

After you create a pipeline, you can view its detail page to monitor SLO breaches, success rate, and latency, and explore SLO-breaching transaction IDs.