Mule Cloud Application Instances Logs Test

Cloudhub provides access to log data for applications deployed on it. These application logs contains information related to the exceptions or failures encountered by the application instances. Administrators use these log files not only to spot problem conditions, but also to troubleshoot them. By periodically scanning the log file of the application instances for errors/failures, the Mule Cloud Application Instances Logs Test promptly notifies administrators as soon as a new error, fatal, warning, or informational message is logged in the file. This way, administrators can proactively track down any failure conditions or exceptions.

This test reports the messages logged in the log files such as error, fatal, warning, debug, or console messages and help administrators to detect any frequent failures or exceptions and drill down more on to the details of the problem conditions.

Target of the test : A Mule ESB Cloud

Agent deploying the test : A remote agent

Outputs of the test : One set of results for each environment:application:instance in the target Mule ESB Cloud being monitored.

First-Level Descriptor: Environment

Second-Level Descriptor: Application

Third-Level Descriptor: Instance

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed

Host

The IP address of the host for which this test is to be configured.

Port

The port number at which the specified host listens.

Username and Password

By default, the eG agent uses the Cloudhub API version 2 (v2) to collect the metrics from the target Mule ESB Cloud or Cloudhub. To be able to connect to the Cloudhub API v2, the eG agent should be configured with the username and password of a user who is vested with the read only rights. Specify the user and password in the Username and password text boxes.

Confirm Password

Confirm the password by retyping it here.

Organization Name

To enable the eG agent to monitor a particular organization on Anypoint platform account, specify the name of that organization against this parameter. For instance, org. Doing so will enable the eG agent to monitor each of the components within the specified organization.

Exclude Environments

Here, you can provide a comma-separated list of environments that you do not want to monitor. For instance,Sandbox,Design,Production,.... By default this is set as none, indicating that this test will report metrics for all the environments on the target Anypoint platform.

Exclude Applications

Here, you can provide a comma-separated list of applications that you do not want to monitor. For instance,Helloworld,AppName,.... By default this is set as none, indicating that this test will report metrics for all the applications on the target Anypoint platform.

Session Timeout

Indicate the duration (in minutes) for which this test should wait for a response from the Anypoint Platform. By default, this is set to 60 minutes. This means that any user session that has remained inactive for more than 60 minutes will be automatically logged out from Anypoint platform. You can provide a duration between 15 minutes and 180 minutes in this text box.

Log Limit

By default, Log Limit is set as 100. This implies that the each time the test runs, it will consider only the first 100 logs for monitoring. You can provide a value between 1 and 2000 in this text box.

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

Error logs

Indicates the number of error messages logged in the log of this application instance.

Number

Error messages are generated when any exception occurs in the performance of the application instance.

The detailed diagnosis of this measure helps to find out the details of the error logs such as Logger name, Thread name, Log timestamp, and Log message.

Fatal logs

Indicates the number of fatal messages logged in the log of this application instance.

Number

Fatal messages are generated when an application fails.

The detailed diagnosis of this measure helps to find out the details of the fatal logs such as Logger name, Thread name, Log timestamp, and Log message.

Informative logs

Indicates the number of informative messages logged in the log of this application instance.

Number

 

System logs

Indicates the number of system messages logged in the log of this application instance.

Number

System messages indicates about application and worker start up.

Console logs

Indicates the number of console messages logged in the log of this application instance.

Number

Console message are about console events such as setting the object store.

Warn logs

Indicates the number of warning messages logged in the log of this application instance.

Number

The detailed diagnosis of this measure helps to find out the details of the warn logs such as Logger name, Thread name, Log timestamp, and Log message.

Debug logs

Indicates the number of debug messages logged in the log of this application instance.

Number