Unable to compare Dynatrace Traces with HANA Cockpit Queries by Timestamp #345
Description
We have a cap-js based application where we’ve instrumented the telemetry-to-dynatrace configuration to export metrics and traces to Dynatrace.
Currently, we’re facing an issue where we’re unable to perform an exact comparison between a database transaction shown in a Dynatrace trace and the corresponding query in HANA Cockpit at the same timestamp. This is because the timelines in HANA Cockpit statements are not directly comparable with the client-side timings displayed in Dynatrace. Additionally, we don’t have a custom correlation methodology in place to bridge this gap.
In the screenshots below, you can see a DELETE statement along with the client-side start time of the trace and the duration of the specific transaction:
Even when we try to compare the exact same DELETE statement at what appears to be the same moment, we are still unable to map the client-side timings from the trace to the start times in HANA Cockpit. This discrepancy is likely due to processing delays or timing differences between the client and database layers.
To help make this mapping more accurate, could you please enable a feature such as SQLCommenter? With SQL comments embedded in the queries, we could tag transactions with a unique identifier (such as the parent trace ID), allowing us to correlate them precisely across both Dynatrace and HANA Cockpit—without relying solely on timestamp alignment.