eG Monitoring
 

Measures reported by BobiEventSvrTest

The Event Server monitors the system for events, which can act as a trigger for running a report. When you set up an event trigger, the Event Server monitors the condition and notifies the CMS that an event has occurred. The CMS can then start any jobs that are set to run upon the event. The Event Server manages file-based events that occur in the storage tier.

If the Event Server is unavailable or slow, the CMS will receive no intimation regarding the occurrence of an event or may receive intimations rather late. As a result, critical jobs that CMS is configured to start upon the occurrence of an event may either not start at all or may take too long to begin. This can have serious repercussions on the performance of the SAP BOBI platform. To avoid this, administrators will have to run the BobiEventSvrTest test at pre-configured intervals.

This test monitors the availability and thread pool size of the Event Server continuously, so that the failure of the server and bottlenecks in event processing (owing to improper thread pool sizing) can be captured quickly and addressed.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
healthState Indicates the current health state of the Event server in the monitored node.   The values that this measure can report and their corresponding numeric values are discussed in the table below:

Measure Value Numeric Value
Danger 0
Caution 1
Healthy 2

If the server is not healthy, then the detailed diagnosis of this measure, if enabled, provides the process ID of the server.

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the health state of the server. In the graph of this measure however, the same is represented using the numeric values only.
serverRunningState Indicates the current running state of the Event server.   The values that this measure can report and their corresponding numeric values are discussed in the table below:

Measure Value Numeric Value
STOPPED 0
STARTING 1
INITIALIZING 2
RUNNING 3
STOPPING 4
FAILED 5
RUNNING_WITH_ERRORS 6
RUNNING_WITH_WARNINGS 7

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the running state of the server. In the graph of this measure however, the same is represented using the numeric values only.
serverEnabledState Indicates whether/not the Event server is enabled.   The values that this measure can report and their corresponding numeric values are discussed in the table below:

Measure Value Numeric Value
Disabled 0
Enabled 1

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not the server is enabled. In the graph of this measure however, the same is represented using the numeric values only.
busyServerThreads Indicates the number of server threads that are currently servicing requests. Number If this measure reaches the configured maximum thread pool size for the server, new requests to the server would have to wait until a server thread becomes free. If this happens often, it may significantly slowdown request processing by the server. In such a situation, you may want to consider resizing the thread pool.
auditEventsInQueue Indicates the number of auditing events that the Event server has recorded, but which have not yet been retrieved by the CMS Auditor. Number If this number increases without bound, it could indicate that auditing has not been configured properly or that the system is heavily loaded and generating auditing events faster than the auditor can retrieve them. When stopping servers, it is advisable to disable them first and wait for auditing events to be fully retrieved and this queue becomes empty. Otherwise, they may be retrieved only when this server has been restarted and the CMS polls for them.