SiteScope : event mapping : custom attribuite to BSM

Hi experts,

I have edited event mapping in SiteScope in order to send custom attributes in the event to BSM.

However, from BSM side I can not find those custom attributes.

Please help,

Elmassimo

Parents
  • I want to rectify the error.

    When using the default cma1 to cma5, the custom attribute is retreived on BSM.

    When creating a new key, the custom attribute is not synchronized to BSM.

    I am searching for a possibility to tell BSM that a custom attribute called X will be sent from SiteScope.

     

  • Verified Answer

    Everything works as designed. Even though UI allows you to add your own custom attributes, the log file policy that handles the events behind the scenes is not updated, so there is no supported way to add arbitrary custom attributes to SiteScope events from SiteScope itself. You are limited to using cma1...cma5 attributes only.

    The workaround I used for my customers would be using SiteScope tags to emulate the custom attributes you want to pass as part of SiteScope events. Once you marked the desired SiteScope monitors with relevant tags, you can use any of cma1...cma5 attributes to contain the value of <<tag>>. It will pass to that OOB cma the comma separated list of tags representing your info. Every tag is in form of a colon delimited name:value pair. In other words in OMi such SiteScope event will have e.g. cma1 custom attribute with the value of tag1:value1,tag2:value2,tag3:value3

    Then it's just a matter of a simple EPI script that will parse the comma separated list from cma1 and create real custom attributes tag1, tag2, tag3 with their desired values.

Reply
  • Verified Answer

    Everything works as designed. Even though UI allows you to add your own custom attributes, the log file policy that handles the events behind the scenes is not updated, so there is no supported way to add arbitrary custom attributes to SiteScope events from SiteScope itself. You are limited to using cma1...cma5 attributes only.

    The workaround I used for my customers would be using SiteScope tags to emulate the custom attributes you want to pass as part of SiteScope events. Once you marked the desired SiteScope monitors with relevant tags, you can use any of cma1...cma5 attributes to contain the value of <<tag>>. It will pass to that OOB cma the comma separated list of tags representing your info. Every tag is in form of a colon delimited name:value pair. In other words in OMi such SiteScope event will have e.g. cma1 custom attribute with the value of tag1:value1,tag2:value2,tag3:value3

    Then it's just a matter of a simple EPI script that will parse the comma separated list from cma1 and create real custom attributes tag1, tag2, tag3 with their desired values.

Children