Splunk AppDynamics

Can the frequency tag be configurable in rest-api while pulling data from AppDynamics.

Rahul_Pola
New Member

I am using time-range-type=BETWEEN_TIMES in the rest-api and pulling data of 15 days time period. i.e.,(from 14th june 2022 to 29th June 2022). 
The response I am always getting with frequency  SIXTY_MIN. Can this be Configurable? Or it's decided by the AppDynamics internally.

Sample response

<metric-data>
        <metricId>160179877</metricId>
        <metricName>BTM|Application Summary|Average Response Time (ms)</metricName>
        <metricPath>Overall Application Performance|Average Response Time (ms)</metricPath>
        <frequency>SIXTY_MIN</frequency>
        <metricValues>
       ......

I am looking to change that frequency to another value like 5 min or 10 min when querying for 15 days older data.
It that can be configurable in the API. Could you please share the api here.

Thanks & Regards,
Rahul
Labels (3)
Tags (2)
0 Karma

Philippe_Thero1
Explorer

Rahul, you may be able to use the rollup feature to get better granularity (rollup=false).
As Kenji said, aged data is aggregated and the base data is then deleted.
However, you can change the number of days after which this happens, this is a controller level setting AFAIK.

regards

0 Karma

Kenji_Kumada
Path Finder
Thank you for your post to the community!
 
Unfortunately, the frequency for the metrics data from the metrics REST APIs is not configurable. It is internally set based on the provided time interval and duration.
In general, shorter duration gives smaller frequency. You can use the following table as a rough reference (This may be different in versions.)
Duration in mins <= 260 = 1 min frequency
260 < Duration in mins <= 2940 = 10 min frequency
2940 < Duration in mins = 60 min frequency
Please keep it in mind that the controller rolls up the old metrics data as per the policies. Therefore, requesting short duration for an old time range gets larger frequency than the one mentioned above. You can have a look to this documentation for the retention and deletion policy:
You can check the retained data with the smallest granularity in the metrics browser's graph. This is also described in the documentation.
There was a similar question in the community. This also may help you to understand the behavior.
Hope this answer helps!
Best regards,
Kenji
Get Updates on the Splunk Community!

Splunk Observability Synthetic Monitoring - Resolved Incident on Detector Alerts

We’ve discovered a bug that affected the auto-clear of Synthetic Detectors in the Splunk Synthetic Monitoring ...

Video | Tom’s Smartness Journey Continues

Remember Splunk Community member Tom Kopchak? If you caught the first episode of our Smartness interview ...

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud?

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud? Learn how unique features like ...