Transactional RFC Activity situation alerts on SAP Agent
Albook 120000625S Visits (6579)
ITCAM for Application SAP Agent provides an attribute group, called
While working with this attribute group, we noticed that a situation was closed almost immediately after it fired, despite the condition was still true,
at least looking at the information in the workspace view "Transactional RFC Status Information".
After having investigated about the method used to collect data for this attribute group, we understood the root cause for this scenario.
First of all, let's consider the situation interval, that was really small, only 30 seconds.
In an SAP environment, some attributes are available as snapshot data while others are collected using a given time span, basically from a begin date to an end date (date + time).
All attribute groups that contain the sample_interval_end attribute are capable of returning data over a given time span.
By default, the workspaces provided by the Monitoring Agent for mySAP request data for the default time span.
So basically, when you refresh a TEP view, the ABAP code running on SAP returns data collected basing on a time span that is different than the one use by the situations.
Let's suppose that you get a new entry in the Transactional RFC Status Information view, if you have a 30 seconds interval situation with a formula that matches one of the value showed in the rows,
This is actually working as designed.
We have two possible solutions for it:
1) Increase the situation interval. If you set it to 5 minutes, it means that the situation alert will remain open at least for 5 minutes, if you use 10 minutes it will stay open for 10 minutes and so on.
Step 1: Logon to SAP GUI and go to transaction code /n/i
Step 5: restart the agent
Hope it helps
Subscribe and follow us for all the latest information directly on your social feeds: