End-User Experience Monitoring (EEM) – Activating Custom attributes
Custom attributes, assigned to EEM robots, can be easily activated. It gives you the possibility to improve your view to the running robots. We will go step by step through the activation of the attribute fields.
A good way to group your robots is to define pseudo locations by using the default functionality as shown below (Fields “Region”, “Country” and “Location”). Of course, you can assign additional custom attributes to the EEM robots as well.
Activating the custom fields allows you to attach additional information about your robots. This can be a contact person for the location of this robot, a geo coordinate, or something else – related to the robots.
In our sample we will add a geo location and the name of a responsible person to the robot.
Step 1 – create the fields
– Open transaction SE16
– Provide the table name: “EEM_LOC_LEVEL”
– Create a new entry with “F5”
Create two new entries, one for coordinates and one for the responsible person. Leave the field “LOC_LEVEL” empty to prevent them showing up in the monitoring UI. Use the names “Coordinates” and “Responsible”.
If you return back to step “2.6 Configure EEM Robots” within the “Solution Manager Configuration Work center” you will see two more columns where you are able to define the additional data as shown below (the two new columns “Coordinates” and “Responsible”).
If you provided a numeric value in the field “LOC_LEVEL” the new data can be seen within the EEM configuration as well as in the EEM Monitoring UI. Another place could be within a tool which is using the data to show them in a map view as shown below:
See more details in the EEM Documentation here:
Other EEM related blogs:
Can I monitor non SAP URL's through EEM. For example I record a HTTP script giving a non SAP URL just to check it's availability and assign a robot to it. Can EEM show the availability of the URL. Could you please clarify?
every http(s) URL can be monitored. The answer is clearly YES.
The scripting tool doesn't care if the monitored system is an SAP backend or not. The missing functionality in such a setup would be the missing backend monitoring. The great features of root cause analysis would be missing. However even non SAP systems can be included in the backend monitoring in certain cases (if Wily Introscope is in place).
Thanks for the clarification. I get an status 506 Authentication error. I have given the details in the discussion EEM non SAP HTTPS URL monitoring . Could you please clarify the error..
See my answer there.
I need some help regarding EEM rfc scripts and deployment
Could you please share you email id with me .
as your issue is not related to the original post, please open a new discussion in "http://scn.sap.com/community/it-management/alm/solution-manager". If you do so others can help as well and potentially learn from all the different answers. Fell free to send a link the your new ost once you created one.
Thanks for your quick reply and precious suggestion. I have opened a new discussion regarding EEM, named "EEM Scripting (http, gui, rfc)" link as follows:
Your valuable suggestions will be highly appreciated.