Share via

The Metric value difference between Azure Portal and Dynatrace Metric

Dsouza, Jovita 0 Reputation points
2025-12-08T14:33:54.2133333+00:00

Hi Team, I’ve noticed a discrepancy between the Azure Portal capacity values and those shown in Dynatrace, even when using the same 10-minute resolution. In Dynatrace, there are spikes reaching 100%, whereas in the Azure Portal, usage remains below 1%. What could be the cause? We are fetching the metric using the Azure Public API integration method.

Azure API Management
Azure API Management
An Azure service that provides a hybrid, multi-cloud management platform for APIs.
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anurag Rohikar 3,110 Reputation points Microsoft External Staff Moderator
    2025-12-08T15:08:59.67+00:00

    Hey Dsouza, Jovita! It looks like you're experiencing a discrepancy between the capacity values shown in the Azure Portal and those in Dynatrace, despite using the same resolution. This kind of inconsistency can be frustrating, so let's explore some possible reasons.

    1. Metric Reporting Differences: The Azure Portal and Dynatrace might be interpreting and aggregating the metrics differently. Make sure that both are set to the same aggregation method (e.g., Average, Maximum) and that they’re pulling data for the same time frame.
    2. Sampling and Delays: Metrics in Dynatrace could be showing spikes due to sampling fluctuations or temporary delays in metric reporting. Azure's reporting might smooth out these fluctuations.
    3. Capacity Metric Updates: It's also worth noting that changes were made in May 2025 to improve the accuracy of Azure's capacity metrics, which can cause discrepancies in reported values. If you're using the Azure public API integration for fetching metrics, ensure that you’re updated about any changes to how these metrics are calculated.
    4. Resource Differences: Make sure both tools are monitoring the exact same resources (API Management instance, settings, etc.). A mismatch could contribute to the differences.
    5. Public API Integration Method: Check the API integration settings and queries in use to ensure that they are correctly configured to retrieve comparable metrics.

    To further diagnose the issue, here are some follow-up questions that could help clarify:

    • Are both systems pulling data for exactly the same resource and time interval?
    • What aggregation method are you using in both Azure and Dynatrace?
    • Have there been any significant changes to your resources or API Management configurations recently?
    • Are there specific metrics (e.g., CPU, memory) that are particularly different, or is it a general mismatch across all metrics?
    • Have you investigated if there are any limitations or issues with the Azure API integration that might affect data reporting?

    Let me know if this helps or if you have more details you can share! Here are some useful resources you might check out for more information on capacity metrics in Azure:

    Hope this helps!

    Note: This content was drafted with the help of an AI system.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.