Update Dynatrace Integration to Use New API (No Key Request Marking)
complete
H
Harlequin Marmot
Hi Harness Team,
I'm reaching out to request an update to our Harness Dynatrace integration. Currently, our setup requires marking requests as key to collect metrics. However, due to our limitations, we can't mark any key requests, which is blocking us from fully utilizing Continuous Verification (CV).
Switching to the new Dynatrace API would remove this dependency and also allow us to capture infrastructure metrics from the pods we deploy—something the current integration doesn't support. Metrics should not be limited solely to services in Dynatrace; infrastructure metrics need to be included as well.
Key Benefits:
Eliminate Current Limitations:
By removing the need to mark key requests, we can collect comprehensive metrics without relying on a workaround.
Enhanced Monitoring:
The new API will provide full visibility, including infrastructure metrics from our deployment pods. Currently, custom metrics are tied only to key requests, which restricts our ability to monitor metrics beyond that scope.
Log In
Prasad Satam
updated the status to
complete
Thank you for raising this. The Harness CV integration with Dynatrace has been designed so that the "key request marking" API is only required when using Metric Packs. If you are configuring metrics directly — which is the recommended approach — the new Dynatrace API works seamlessly without this constraint. This request is addressed through the current integration design. If you are using Metric Packs specifically and need further assistance, please reach out to Harness Support and we will be happy to help.