Conversation
Preview links (active after the
|
| description: Monitoring transaction processing with Data Streams Monitoring's Business Transaction Tracking | ||
| --- | ||
|
|
||
| {{< callout url=https://www.datadoghq.com/product-preview/business-transaction-tracking/ |
| - 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. |
There was a problem hiding this comment.
I want to make sure the extractors are not a blocker since we can add new ones if there's demand. Maybe rephrase to something like:
...extracts transaction IDs from sync (like HTTP request/response) and async (like Kafka produced/consumed) message headers.
|
|
||
| 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 |
There was a problem hiding this comment.
This part is currently gated so they'll need to contact us to get access to the page
|
|
||
| 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 |
There was a problem hiding this comment.
Is it possible to add a screenshot of the outcome before the creation process? I can provide a good screenshot (our demo env is a bit unstable so need to look at a good data point). Things to highlight:
- Summary metrics - monitor business transactions SLO breaches, success rate, and latency
2. Identify individual transaction IDs breaching SLO so you can take action
3. Find APM traces of transactions to speed up troubleshooting
This could be repetitive to the value prop mentioned above so lmk if you have thoughts on how to incorporate without duplicating
| - <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>. |
There was a problem hiding this comment.
Is this line and the "Click Done" line meant to be indented with no bullet or numbered list? Just looks a little off to me.
Co-authored-by: Brett Blue <84536271+brett0000FF@users.noreply.github.com>

What does this PR do? What is the motivation?
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes