PurePath Filter Options
In dT 5.6, I have an application that is generating sooo many keepalive transactions I can't find the true application transactions in the sea of noise. In the filter, I see there is a way to search for a purepath, is there an operator that will allow me to filter out these keepalives ? Something like "Contains: <> keepalive()".
Also, how do I head these off at the start? Is there somewhere in the System Profile where I can just set the system to not record these keepalives from the get-go?
Thanks
George,
It looks like your method sensor rules aren't quite right. The easiest way to do them might be to open up the PurePaths and right-click on a method in the lower pane, then select "Exclude Selected Methods". Once you've gone through the sensor creation process for both of the methods, open up the system profile --> sensors and change the "exclude" to "global exclude" for both methods.
Also, it's counter-intuitive, but you want the global exclude to be "active", not "inactive" as you have them.
-- Graeme
I tried this, the app was restarted this weekend, and I'm still seeing these keepalives. Am I missing something? I'm attaching the current settings.
Well - it will just get rid of the isAlive method itself but the PurePath that gets started on your "dispatch" method will still be captured.
If all your PurePaths (also the ones you are interested in) are coming in through "dispatch" then excluding this method may stop collecting all of your Purepaths -> which is not what you want. But - give it a try: Also globally exclude "dispatch" and see if the PurePaths you are stilil interested in are still captured. If it works the PurePaths will most likely start with the next method down which should also be picked up by our RMI Sensor.
please give this a try
This is what I have. Does the exclude look right?
In this case the only thing you can try - if possible - is to globally exclude these entry point methods. However - if they all come in through the same RMI Interface then thats probably not an option either. If there are however different methods for these keepalives as compared to those that are of interest to you then you could try global exclusion rules for these methods
This is a client - server application. There are no URL's. These are all RMI transactions.
Hi George
Are these coming in through a specific keepalive URL? If so you can exclude this URL from the Servlet/ASP.NET/Web Server Sensor. In the System Profile you can edit the properties for these sensors and define exclusion URLs - these are URLs that will then NOT START a PurePath
Andi
