Boomi Audit Log Test

In Boomi, an audit log represents the events that occur within the Boomi platform, typically related to process execution and integration operations. The audit log helps track and monitor events, providing a way to review what happened during a process execution, and when they occurred. It is useful for troubleshooting, security, compliance, and maintaining oversight of integration tasks. This test reports the events generated by the target Boomi AtomSphere.

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.
Include Log Level	Specify the log levels in the Include Log Level text box. For example, the log levels include log information, debugs, errors or warnings. Provide comma separated values if there are more than one log type.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Info log count	Indicates the number of service related information events.	Number	A change in value of this measure may indicate infrequent but successful operations performed by one or more applications. The detailed diagnosis of this measure lists the information log details that include Log date, Document id, Message Container id, Account id, User id, Type, Action, Modifier, and Source.
Debug log count	Indicates the number of debug events.	Number	The detailed diagnosis of this measure lists the debug log details that include Log date, Document id, Message Container id, Account id, User id, Type, Action, Modifier, and Source.
Warning log count	Indicates the number of service related warning events.	Number	If a process consistently generates warnings, it might lead to performance degradation. This is because more system resources are being used to process and log the warnings, which could potentially slow down the integrations over time. Ideally, the value of this measure should be low. The detailed diagnosis of this measure lists the warning log details that includes Log date, Document id, Message Container id, Account id, User id, Type, Action, Modifier, and Source.
Error log count	Indicates the number of error events.	Number	A very low value (zero) indicates that the system is in healthy state. The detailed diagnosis of this measure lists the error log details that includes Log date, Document id, Message Container id, Account id, User id, Type, Action, Modifier, and Source.