AppD Archive

Not happy with Lite, its not at all monitoring

CommunityUser
Splunk Employee
Splunk Employee

Hi,

We wanted to see how app dynamics helps in our project so we have configured on our dev server but its not able to monitor anything. Please find the below:


I’ve been playing with AppDynamics on the DEV server all day, trying to fire in as much data as I can in order to get it to do… something. So far, it only really seems to have detected our logging software and one other method. I have tried disabling all of the transaction detection types and leaving one at a time open, but these are the only things it picks up on.

I have also tried to disable all but the transactions it is actively monitoring – AppDynamics itself and all of the guides say that it can only monitor 30 processes at once, and I must exclude ones I do not want to monitor. However, when I do exclude the ones that do not seem to be being monitored, it does not pick any others up at all, leading me to believe that it can only detect 30 processes in total, but I know that we have more than that.

I am also unsure about the static ms limit for determining whether a particular process is slow – I know that you can set up separate alerts for separate processes – surely this is quite redundant, as a page redirection action that passes a session to another JSP page would have completely different definitions of ‘slow’ than a large database call?

Finally, I am a bit wary of the method by which we can choose exactly what we monitor – I would like to be able to explicitly choose the 30 processes that we would like to monitor, and set up alerts for each based on its average latency, but other than ‘let AppDynamics find them and then exclude until it picks the right ones for you’ there doesn’t seem to be any way of explicitly tailoring it to your needs.

could you please answer above questions?

(PS – screenshots below show the transaction screen showing before and after excluding methods that are reporting no calls (even though I know some of them are getting calls at least). As it shows, AppDynamics just excludes the 28 I don’t want, without repopulating it like the guides say it should)

0 Karma

Arun_Dasetty
Super Champion

Hi,

We understood your concerns, please find the response to your queries inline:

>>>> Query regarding max 30 transactions limit reached error message shows though excluding the BTs discovered and generating new load?

Answer: we are apologethic for this as we have known issue in Lite version and we already filed a high priority internal bug for this and is targeted to fix this issue in future LITE version of the product.

Please be sure that this issue does not exists in our Pro version of AD controller.

>>>>> the static ms limit for determining whether a particular process is slow – I know that you can set up separate alerts for separate processes – surely this is quite redundant, as a page redirection action that passes a session to another JSP page would have completely different definitions of ‘slow’ than a large database call?

Answer: We understood your query as listed below:

- you have different BTs and with different slow response time, in brief, there are certain BTs that response times for which are usually takes bit longer time compared few other discovered BTs. If this is the case, let us know if the following infromation helps:

- Let us know whether switching from static thresholds under Configure -> Request Threshold -> slow threshold section, from static option to threshold based on percentages or standard deviation option helps

We see that currently setting different thresholds for different BTs is a limitation in current LITE version of the product, However we would like to inform that you can set different threshold options at each BT level in our Pro version of the AD product, as opposed to LITE version of the product

>>>>> let AppDynamics find them and then exclude until it picks the right ones for you’ there doesn’t seem to be any way of explicitly tailoring it to your needs?

Answer: Currently in Lite Version it is limitation to customize the BT configuration and defining custom rules which could help to meet your requirement where you can define custom servlet rules to group certain BTs and define exclude rules on BTs that you are not interested in, However our Pro version of the product supports help to customize transaction detection so that BT limit can be controlled.

we request you to go ahead and try out  free trial of AD Pro version and check whether our pro version meets your requirement of customizing the transaction detection and also we would like to inform that our pro version have default alerts / health rules which could help.

http://info.appdynamics.com/freetrial.html

Let us know if that clarifies your queries.

Thanks,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Answer: we are apologethic for this as we have known issue in Lite version and we already filed a high priority internal bug for this and is targeted to fix this issue in future LITE version of the product.

The bug sill has not been fixed as of Jan 10 2014, months later...

I'm hitting the 30 transactions limit as well even with excluded ones. Is there a preview build I could download ?

0 Karma

Arun_Dasetty
Super Champion

Hi Daniel,

We understood your concern here. We do not have preview LITE build with fix as such. We request you to try free trial of our PRO product where this issue does not exist :  http://info.appdynamics.com/freetrial.html

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi,

Is this issue fixed in lite version ?

Thanks.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Let me clarify Arun's comment -- we have deprecated our old standalone Lite viewer product and have instead launched a new free forever Lite edition, which has the same features the Pro edition plus a couple of restrictions. See explanation here: http://www.appdynamics.com/pricing-appdynamics-pro

You can signup for this Lite edition here: http://portal.appdynamics.com/account/signup/signupForm

First 2 weeks will be a free trial of the Pro edition. If you do not upgrade to a paid version of Pro edition, the product auto-downgrades to Lite edition. This option is available for both On-Premises and SaaS deployment options.

0 Karma

Arun_Dasetty
Super Champion

Hi Ashish,

Support for liteviwer(LITE) version is removed , we request you to try with trial version of PRO and see how it goes.

Regards,

Arun

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 ...