can you trace back a purepath based on tagID
PurePaths can be identified by their tagId.
When I am troubleshooting, at many time, I can indicate one or more purepaths as being suspisious.
Rather then saving the dashboard, I would like just to keep the tag id, to be able to re-find the purepaths quickly. But I do not find any option to filter on tagid (unless you open all purepaths and then use the table-filtering, but this creates lots of overhead and you have to keep other dashboard filters too)
BTW, still using DT 6.3
Hi Monique, yes there is a way. Have a look at the client REST interfaces. In particular, the `purepathid`, `PA` and `PT` filter parameters.
The problem with that is that if you don't also provide a filter AppMon will open a default dashboard where it will analyze the complete (live) session in which the PP resides in - which can take ages to complete and put unnecessary load on the server. Unfortunately providing a good filter manually is often a non-trivial task...
Enrico,
as 'permanent' user of appmon, I experienced you can avoid analyzing too much (overloading server), just by first creating a new dashboard (empty one) then set your filters (like on application and/or host level and/or timing) and then open the appropriate dashboard (like purepaths, database hotspots or whatever)
So using this practice, you could have the option of a filter (simular to business transaction filter, time-filter,...) with as a parameter the purepath-id without overloading the server.
By the way : when I am giving hands-on training to people in our company, I always suggest to work this way to waist no time on server
Hi Monique,
If you mean invoking the openpurepath REST service using only the "purepathid" and "dashboardname" parameters (denoting an existing custom dashboard) then according to my tests this will not work efficiently. In fact, it seems when doing so the PP will open in a copy of the custom dashboard (auto-prefixed with the system profile name) and the timeframe will default to 30 days even if it was set to something else in the original custom dashboard. Thererfore, I conclude that it's almost mandatory to always include a timeframe filter when invoking the REST service or else the client will start analyzing irrelevant session data right away.
Thx Adam, actually I was looking to a way to open a purepath where I know tag-id from within the client. But at least, this is a way to open it...
