Overview

Log Pattern Monitor is a powerful customized monitor that extracts information from log files depending upon the search pattern provided. Extremely useful when you have to abstract specific data from logs like errors, exceptions, warnings etc. These monitors parse logs in real-time which enables users to have complete log observability and identify issues or outliers as they occur. Users can monitor logs from different components like infrastructure, application, network etc.

Platform/OS supported

• Linux
• Windows
• RHEL

Pre Requisites

• To successfully fetch logs from your environment, make sure that the log files that you want to monitor are present
• The application, whose logs are to be monitored, should be up & running.

Configuration of Log Pattern Monitor

Provide the details in the following fields for the configuration of Log Pattern:

 

• Log Pattern Monitors
  • Metric Group Name - To create a GDF of which you have configured monitor by Providing a suitable metric group name under which we will be able to see the metrics being captured.
  • Metric Group Description - To provide a suitable metric group description corresponding to the metric group name.
  • File Name Selection(Use File name) - Getting log using File Name path
  • File Name Selection(Use Command to get the file name) - Getting logs through the command.
  • File Name Selection(Use JournalD) - JournalD is the system service for collecting and storing log data introduced with systemd. Getting log using type “JournalD” and based on the following option:
    • All Logs 
    • Specified Value
• Pattern
  • Search Pattern- Enter the Search pattern via which you want to get the logs i.e. enter the pattern that will be used to search & retrieve the corresponding log lines. 
  • Metric Name - Provide a suitable metric name under which we will be able to see the metrics being captured via search pattern.
  • Unit - Select the unit for metric name in per sec or per min.
• Advance settings
  • Dump Server Logs inside the Test Run - Select this box if you want to dump server logs inside the Test run. This field is basically used for the debugging process for if you have a client server where you are not able to access the data but you can dump the logs on your server and validate the data captured by the monitors by correlating with the captured logs.
  • Read Multiple Log Files - If you want to read two or more logs files, check this box.

Note: For multiple log files, special characters supported in file path are * ? [ ] '{' } ( ) +, else only * is supported at file level.

Deployments of Log Pattern Monitors

• When the configurations have been added, you can go to the deployments screen. In the deployment screen, you will see the configured monitor. You can edit the configurations in the configured monitor in case you want to change the File name selection/Instance Name/Metric group name by clicking on the Edit icon under the Actions column. To delete the selected configured monitor, click on the Delete icon.
• You can deploy the monitors in the deployments screen.

Deploy Monitors

Deploy the configured monitors using our machine agent in the deployments screen. The following fields need to be filled in to deploy:

Tier: Tier is used to select the tier on which the monitor(s) will be deployed. Select the required tier from the drop-down list.

Server: You can select the server(s) of the selected tier on which the configured monitor(s) will get deployed.

• All -Deploy the configured monitors on all the servers of the selected tier.
• Any - Select any one of the servers where monitors will be deployed.
• Specified Server - Select one or multiple servers of the chosen tier on which the monitor(s) will be deployed.

Validation

• To validate the successful implementation of custom log pattern monitor is validated after completing the above fields, it automatically comes on the monitoring homepage UI with the number of monitors are successfully running or failed with details.
• Also, validate the custom log pattern metrics under the given instance name in the metrics tree.