AppD Archive

Requests "lost" from report

CommunityUser
Splunk Employee
Splunk Employee

Hello,

I created a time range to see requests of that time span easily.

When I viewed results two days ago, the total requests number in that time range is 56,051.

When i viewed results of that time range today, the total requests number is 26,495.

I believe I am selecting the correct time range, and think I have seen this issue a coupleof days ago.

Am I missing something? Thanks!

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi,

If my understanding is correct you have created a custom time range to see requests of that time span
and when you see again after a time gap(after two days in this case) the total request number is reduced.

To confirm the issue can you please send us the screenshots for two different dates(with a gap of two days) for the custom time range where you see the  total requests number displayed in controller is reduced.

 

Thanks,

Swapna.

 

 

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi,

I compared data retrieved earlier with the ones I'm looking today:

In the table below, each column contains number of requests read from AppDynamics for a saved time range, there are two rows, one for the number read earlier, one for the number read today.

Please note one of the screenshots in last reply shows "Previous" number of column #2 XXL_1014 as 58,710 (read on Oct 15), is different from the number shown in the table below as 54,899 (read on Oct 17).

  XXL_1009 XXL_1014 XL_1014 L_1015 M_1015 XXL_1018
Previous 38,155 54,899 56,051 60,607 53,915 174,937
Now 38,155 35,180 26,495 106,270 53,915 175,534

Do old data get automatically cleaned up? I'm not sure since one of our oldest test in #1 column shows the same numbers. 

This starts to make me inconfident about the previous results, and our analysis based on them. Do you have any updates on this please?

0 Karma

Arun_Dasetty
Super Champion

Hi,

We expect that metric/call statistics data recorded in UI, should not lost but will be rolled based on retention settings as stated in docs, we request you to go through the logs and let us know if this is the case:

http://docs.appdynamics.com/display/PRO13S/Database+Size%2C+Data+Retention%2C+and+Metric+Resolution

Thanks,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Arun,

Thanks for the reply and link to the documentation, it makes sense to me.

0 Karma

Arun_Dasetty
Super Champion
Hi,

Glad to hear that the provided docs helped to clarify the difference in
stats for different time resolutions.



0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Swapna,

 

Thanks for the reply. I've attached two screenshots, though showing requests from a different time range from the one I specified in the initial post.

 

In requests_20131015.png, it shows there are 58,710 requests; in requests_20131018.png, it shows there are 35,180 requests in the same time range. I've confirmed I chose the same application when taking the screenshots.

 

I found today that in another previously saved time range, the number of requests increased than the last time I saw it.

 

Thanks for your help!

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...