How to get all the required details from split in a single purepath details.

How to get  all the required details from split in a single purepath details.

I have a Business Transaction with 2 splitting’s,  page and widget. I have more than one widget in a single page.

Currently I am getting page name and one widget name in following format. “page name; widget1”.

But I want to get all the widgets in the splitting’s.

“page name; widget1”

“page name; widget2”

.

… etc.

Let me know how what settings to be changed in the BT to achieve this

Are you talking about UEM or Server Side PurePaths? Also, are the widgets named differently?

Example:

HomePage has 4 widgets, but all widgets are PanelWidgets.  Your BT would be created against the PanelWidget but wouldn't diferentiate it because they all are named the same in your splitting. There is no way to make them different, unless they call uniquemethods, or if there is an arugment value that would make them unique.

However, if the following is true:

HomePage has 4 widgets; 2 PanelWidgets, a RSSWidget, and a AdvertisementWidget.  Your BT would need to have all of these widgets listed in the splittings.

Also in this example, if your widgets are all named something like MyNamespace.MyClass.Widgets.[WidgetClass]. You could use the Methods - Classname Splitting and create a regex to look at the following MyNamespace.Widgets.* This would evaluate all of the widget classes.

You need to make sure you are instrumenting this class in a custom method sensor or it won't get picked up.

So, if I'm reading this correctly, you have a sensor placed on getName() that is part of your widget classes. Your home page calls getName from this class at some point and that is what you are keying off of.

Example class and method names, <Namespace>.<ClassName>::<MethodName>::

MyWidgets.Accountportlet::getName()
MyWidgets.Userportlet::getName()
MyWidgets.Addressportlet::getName()
MyWidgets.Registrationportlet::getName()

I would first make sure I had a sensor rule that caught all of the classes that could be of interest by using a regex sensor rule; in my case MyWidgets\..*portlet. I would then make sure that I was only capturing the getName() method. You could of course create a sensor rule that uses inheritance and automatically pulls the super classes as well. I used regex for simplicity.

Secondly, I would create a measure that matched the placed sensor with the same regex. MyWidgets\..*portlet. I have named it SPLITTING - Portlet Classes; to make sure I know exactly what my measure is supposed to provide. This splitting is based off of the Methods - Classname Value measure.

With these two items created, your business transaction can use the new SPLITTING - Portlet Classes splitting and it should start to work. By using the regex for commonly named class names, you get the added benefit of picking up ALL classes not just the one or two you're looking for in the first place. As I said, you could also create a sensor placement that used inheritence in combination with the same splitting and it should provide the same effect.

Also,

Please make sure that you have "Only analyze the first method occurrence per Purepath" unchecked.

Let us know if that helps.

Thanks,

Harshal.