Splunk AppDynamics

Metric Data using REST API - Faulty frequency in older timestamps

Ashmita_Thapar
Explorer

Hi

I am trying to request metric data from my controller using metric-data rest api. Though, the frequency of data points is showing some inconsistent behaviour while giving time frame of current data and older dates.

e.g. Fetch Business Transactions' Calls per minute metric data for 15 minute frame in today.

Frequency - ONE_MIN in response and number of data points is 15 which is accurate.

But for older date, say 9th May 2022 data being requested on 11th May 2022 for a data frame of 15 mins, similar to above scenario. Then,

Frequency - TEN_MIN in response and only 1 data point which is inaccurate.

Note: rollup is false in both cases.

https://xx.saas.appdynamics.com/controller/rest/applications/xx/metric-data?metric-path=Service+Endp...

[
    {
        "metricId": 2960604,
        "metricName": "BTM|Application Diagnostic Data|SEP:211315|Calls per Minute",
        "metricPath": "Service Endpoints|xx|/xx|Individual Nodes|baseapp|Calls per Minute",
        "frequency": "TEN_MIN",
        "metricValues": [
            {
                "startTimeInMillis": 1652107200000,
                "occurrences": 1,
                "current": 141,
                "min": 0,
                "max": 167,
                "useRange": true,
                "count": 10,
                "sum": 1264,
                "value": 126,
                "standardDeviation": 0
            }
        ]
    }
]

 Urgent help required over this one...

Labels (3)
Tags (2)
0 Karma
1 Solution

Morelz
Builder

Hi Ashmita

What you are describing is exactly how it works.

Raw per minute data is no kept indefinitely , it is aggregated at certain time periods and stored in the aggregated time sections.

You can read more here which explains how that works

https://docs.appdynamics.com/22.5/en/appdynamics-essentials/metrics-and-graphs/metric-data-resolutio...

Ciao

View solution in original post

Ashmita_Thapar
Explorer

Adding to my set of observations, in older dates if i request data for timeframe less than ten minutes long e.g. 5 minutes. Then, the data set is empty and no data points are returned.

0 Karma

Morelz
Builder

Hi Ashmita

What you are describing is exactly how it works.

Raw per minute data is no kept indefinitely , it is aggregated at certain time periods and stored in the aggregated time sections.

You can read more here which explains how that works

https://docs.appdynamics.com/22.5/en/appdynamics-essentials/metrics-and-graphs/metric-data-resolutio...

Ciao

Ashmita_Thapar
Explorer

Hey Mario,

Thanks for answering my doubts. Even though i understand the concept, but i would like to understand the difference between behaviour of UI and Rest. The UI is still capable to plotting the data with frequency ONE_MIN whereas the same time frame is served with minimum frequency TEN_MIN for rest. 

Also, the minimum TEN_MIN frequency restricts user from accessing data if the time frame of interest is smaller than 10 minutes.

Get Updates on the Splunk Community!

Splunk AI Assistant for SPL | Key Use Cases to Unlock the Power of SPL

Splunk AI Assistant for SPL | Key Use Cases to Unlock the Power of SPL  The Splunk AI Assistant for SPL ...

Buttercup Games: Further Dashboarding Techniques (Part 5)

This series of blogs assumes you have already completed the Splunk Enterprise Search Tutorial as it uses the ...

Customers Increasingly Choose Splunk for Observability

For the second year in a row, Splunk was recognized as a Leader in the 2024 Gartner® Magic Quadrant™ for ...