Is there an way to drill down to a web service with issue
I think the answer is NO.. but wanted to check still... Now I got this alert where a warning of web service being greater than say 200ms.. Rather than looking into the purepath by limiting the time frame, is there an easier way to drill down to the web service which may have caused this. there are many web services in this situation....
Jibi
Dominik - Details shows me the agents involved and the values and also the involved measures. Just 1 measure in my case as it is an avg web serrvice time.
Thanks James, Dominik & Thomas.
I did n't know there was this option to drill down to PP from Incidents.
Hi Jibi,
Have you opened up the Incidents dashlet as James mentioned? From the Incidents dashlet you are able to expand on the incident you'd like to drill down on. Once the incident is expanded you can then right click on one specific violation and drill down to PurePaths. This will show you the specific PurePath(s) that caused the incident to be triggered. From the PurePaths you will then have the option to drill down to just web services.
Just one addition to this. While the Drill Down works it will not just open the PurePaths that caused that Incident but it will open the PurePath dashlet with a filter on the measures that caused that Incident to trigger. So - in your case - it will set a filter on the Web Page Request BT for that particular timeframe. It is most likely that you have some PurePaths in there that did not take that long as they also happened in the same timeframe and were assigned to the same BT
Andi - The only additional filter I see is for Incidents and state.
I am confused now. I am thinking there is no filter on BT or Measure. Please cofirm.
It depends on the Measures used for the Incident. If it is an incident based on a BT Measure then we additionally set that BT Filter. In the example from Thomas we would set that filter. If it is an Incident based on an arbitrary measure, e.g: Counts of DB Calls - then obviously there is no correspoinding Dashlet Filter option. In that case we simply filter by timeframe giving you all PurePaths in that timeframe.
What I want to make sure people understand is that PurePaths are not tagged with -> "PART OF THAT INCIDENT". There is no correlation between Incident and PurePath. There is a correlation between PurePath and Measure. And - if you drill down we try to open the PurePaths with the best filter option available
Andi
The "Details" of the Incidents in the Incident Dashlet contain additional information related to the incident including which measure triggered it. What does it show for you?
Note, the information provided when you "hover" on an incident with the mouse will provide some additional information, not sure why the context-menu "Details" does not show the same here.
James - This is a measure for time - web services. I know the reason for the blip but then it covers all the web services on the site and have difficult isolating the one the caused the issue from the various purepaths or from the web services dash..
You can drilldown to the incidents dahboard from that page the same way you would drill down to the purepaths. That should show you what caused that blip in your heat map.
I can drill down to web services but still feel it is going to need further digging on my end.. atleast in this example I could not figure out easily.
