search cancel

Controller name attribute not available during experience card creation

book

Article ID: 203209

calendar_today

Updated On:

Products

CA Application Performance Management Agent (APM / Wily / Introscope) CA Application Performance Management (APM / Wily / Introscope) INTROSCOPE DX Application Performance Management

Issue/Introduction

We are unable to create the experience card, using an attribute Controller Name. But using the same attribute we are able to create the perspective.  Why is this?

Application is .NET.

 

Still seeing attributes after deleting? Why?

 

 

Environment

Release : 10.7.0

Component : APM Agents

Resolution

From WebEx with customer:

- Confirmed this attribute ControllerName doesn't exist for Experience nodes, therefore not showing up in the list to group by.

- So they might need to add the attribute to the Experience nodes first. There are multiple ways to do that.

      * They can also group Experience Cards on some other existing attributes.

      * Custom Attribute 

Additional Information

Perspective is based on all map nodes, Experience View only for Experience nodes (frontend/bt), so you might have different attribute drop list due to the different scope.

Put it another way: The attribute will show in Perspective dropdown list, if at least one map node has this attribute. But it won't show in Experience View list, unless at least one Experience node also has it

In order to use an attribute to group Experience Cards, at least one Experience node (usually the frontend) needs to have this attribute. If none of your Experience Card has this attribute, you won't see it showing in the list.

To propagate a custom attribute from downstream nodes to Experience node, you need to whitelist the attribute (on both ETC/MOM, same property name), and all next level downstream nodes need to have same attribute name/value.

 


Deleted custom attribute should expire along with the old Vertex.

  •