eG Monitoring
 

Measures reported by SapB1EventsTest

When data is added, changed, or deleted in SAP Business One company databases, SAP Business One creates events in the SEVT table of the SBO-COMMON database. The events contain the company identifier, the object ID and information whether data is new, changed, or deleted. The event sender regularly picks up events, forwards them to the integration framework and deletes them from the SEVT table.

Events are notifications that the integration framework is interested in. Active scenario steps with the SAP Business One inbound channel subscribe to events. SAP Business One inbound retrieves the data matching the event from the company database. For data retrieval, the framework uses the interface that is defined in the inbound channel, either the DI API, the service layer or JDBC. Then, the framework processes the message based on definitions in the scenario step.

Events can have the following status:

  • Success - The integration framework can process the information.

  • Filtered - There is no scenario step subscribed to the incoming event.

  • Failure - Scenario steps that subscribe to the event are not active. You can edit and resend such events.

If the events are completed / forwarded to the integration framework with the Success status, then, message processing will be performed at a faster pace. If too many events are forwarded with the Failure / Filtered status, then, message processing will be delayed leading to unexpected slowdowns in the target SAP Business One. To proactively detect the count of those events with the Filtered and Failure status and prevent slowdowns, eG Enterprise offers the SapB1EventsTest.

This test reports the count of events that were completed with Success, Filtered and Failure status. This test also reveals the rate at which events were completed with Success, Filtered and Failure status. Using this test, administrators can periodically monitor a sudden surge in the count of events that failed, analyze the reason behind such failure events and proactively prevent such failures.

Outputs of the test: One set of results for target SAP Business One being monitored.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
successEvents Indicates the number of events completed with Success status during the last measurement period. Number

 
failedEvents Indicates the number of events completed with Failure status during the last measurement period. Number

Ideally, the value of this measure should be 0. A sudden/gradual increase in the value of this measure is a cause of concern and requires further investigation.

The detailed diagnosis of this measure reports the UserID, Source DB, Timestamp, Object type, Trans type, Field names and Field value generated for the failed events.
failedEventRate Indicates the rate at which events were retrieved with Failure status during the last measurement period. Events/sec

 
filteredEvents Indicates the number of events completed with Filtered status during the last measurement period. Number

By default, most of the events that are triggered on the target SAP Business One may not be useful in a large SAP environment and hence handling all of them would degrade the performance of the environment.

Filtering unnecessary events saves a lot of processing time and ensures that the required events alone are handled and the rest are ignored.
filteredEventRate Indicates the rate at which events were completed with Filtered status during the last measurement period. Events/sec

 
totalEvents Indicates the total number of events completed during the last measurement period. Number

 
totalEventRate Indicates the rate at which events were completed during the last measurement period. Events/sec