Boomi Execution Statistics Test

Boomi Execution Statistics refer to a set of performance metrics and data points that track the execution of integration processes within the Boomi platform. These statistics provide detailed insights into how processes are performing during runtime, helping users to monitor, analyze, and optimize the execution of their integrations. When there are more queued executions in Boomi, it means that there are requests waiting to be processed, but the Boomi Atom has not yet processed them due to limitations in capacity or processing speed. This test helps the administrators identify the issues raised due to queued executions and resolve them before any impact occurs.

Target of the test : Boomi AtomSphere

Agent deploying the test : An internal agent

Outputs of the test : One set of results for the Boomi AtomSphere being monitored.

Configurable parameters for the test
Parameter	Description
Test period	How often should the test be executed
Host	The host for which the test is to be configured.
Port	The port number at which the specified host listens to. The default value is NULL.
JMX Remote Port	This parameter appears only if the mode is set to JMX. Here, specify the port at which the JMX listens for requests from remote hosts. Ensure that you specify the same port that you configured in the management.properties file in the <JAVA_HOME>\jre\lib\management folder used by the target application . To know more, refer to Enabling JMX Support for JREtopic in Monitoring Java Application document.
JNDI Name	This parameter appears only if the mode is set to JMX. The JNDIname is a lookup name for connecting to the JMX connector. By default, this is jmxrmi. If you have resgistered the JMX connector in the RMI registery using a different lookup name, then you can change this default value to reflect the same.
JMX User, JMX Password, and Confirm password	These parameters appear only if the Mode is set to JMX. If JMX requires authentication only (but no security), then ensure that the user and password parameters are configured with the credentials of a user with read-write access to JMX. To know how to create this user, refer to Configuring the eG Agent to Support JMX Authenticationtopic in Monitoring Java Application document. Confirm the password by retyping it in the Confirm Password text box.
Provider	This parameter appears only if the Mode is set to JMX. This test uses a JMX Provider to access the MBean attributes of the target Java application and collect metrics. Specify the package name of this JMX Provider here. By default, this is set to com.sun.jmx.remote.protocol.
Boomi Platform Base URL	Specify the URL - https://api.boomi.com/ that is used towards user registration for accessing the Boomi console.
Account ID	Specify the user Account ID that is auto-generated while registering the user in Boomi console. To know more, refer to Creating a new user and assigning user role in Boomi console topic in How does eG Enterprise Monitor Boomi AtomSphere? chapter.
Boomi User Account	Specify the email ID of the user in the Boomi User Account text box that is used towards user registration for accessing the Boomi console. To know more, refer to Creating a new user and assigning user role in Boomi console topic in How does eG Enterprise Monitor Boomi AtomSphere? chapter.
API Token	Specify the API token value that was generated using the Boomi console. To know how to generate the API token in Boomi console, refer to Creating a new API token in Boomi console in How does eG Enterprise Monitor Boomi Service?chapter.
Timeout	Specify the duration (in seconds) for which this test should wait for a response from Boomi AtomSphere. The default value is 120.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Running executions	Indicates the number of running process executions.	Number	If fewer executions are running, it might indicate that the load or traffic to Boomi process is lower than usual. For example, if the web service is not receiving as many requests, the number of running executions will naturally be less.
Running non-queued executions	Indicates the number of running process executions that were not in queue.	Number	When the count of non-queued running executions is lower than expected in a Boomi execution process, it typically indicates that active process executions are fewer than anticipated, and that these processes are not waiting in the queue to be processed. As a result, the process may not be triggered often enough, resulting in fewer non-queued running executions. For example, if a scheduled trigger is used, the process will only run when the scheduled time arrives.
Running execution estimated count	Indicates the estimated count of running process executions.	Number
Total number of executions	Indicates the total number of process executions.	Number
Average execution time	Indicates the average time taken for process execution.
Queued execution count	Indicates the number of process executions that were in queue.	Number	When there are more queued executions, it means that there are requests waiting to be processed, but the Boomi Atom has not yet processed them due to limitations in capacity or processing speed. The executions will be processed as soon as resources (such as CPU, memory, or execution threads) become available, but there might be delays. If the queue is long, it can lead to slower processing times for users or systems dependent on these processes.
Queued execution estimated count	Indicates the estimated count of process executions that were in queue.	Number
Average queue wait time	Indicates the time spent by the queue in waiting status.
Tasks in queued	Indicates the number of tasks that were in queue.	Number	The overall system processing speed may slow down, as the tasks in the queue have to wait for other ongoing executions to complete. Depending on the number of tasks in the queue and available resources, there may be significant delays before the tasks are processed.
Queued execution timeout	Indicates the time spent for process executions that were in queue.
Local running browsers count	Indicates the number of local running browsers during process execution.	Number
Running browsers count	Indicates the number of currently running browsers during process execution.	Number