A Log Pattern Monitor is used to automatically detect specific text patterns, keywords, or error messages within application or server log files, enabling real-time identification of issues. It continuously scans log data and alerts users when a defined pattern appears, helping teams troubleshoot problems faster and maintain application stability. For example, if logs contain recurring messages like “Database connection failed”, a Log Pattern Monitor can immediately flag each occurrence for quick action.The Log Pattern Monitor continuously scans application and server logs to detect predefined error messages or patterns in real time, enabling quick issue identification and faster troubleshooting.

Custom Log Pattern Deployment

It displays the list of configured monitors. From the Deployment screen, users can deploy the selected monitors by choosing the appropriate Tier and Server. Clicking the Settings icon opens the configuration panel for the selected monitor, where users can view its configuration details.

• File Name Selection: This section allows users to specify how the log source should be identified for applying the Log Pattern Monitor. Based
  • File Name: Enter the name or full path of the log file on which the Log Pattern Monitor should be applied. Example:/var/log/application/app.log
  • Use Command to Get File Name: Use this option to provide a command that dynamically extracts the log file name on which the monitor is deployed. This is useful when log file names change or are generated at runtime. Example:ls -t /var/log/application/*.log | head -1
  • Use JournalD: Select this option to collect logs from JournalD. Users can choose:
    • All logs to scan all available JournalD logs
    • Specified to define a specific JournalD source
• Instance Name: Enter a unique and meaningful name for the Log Pattern Monitor instance. This name helps identify the monitor in the configuration list, monitoring views, and reports.
• Advanced Settings: This section provides additional configuration options for the Log Pattern Monitor.
  • Dump Server Logs Inside the Test Run: Enable this option to include server log details within the test run data. When selected, the collected logs are attached to the test run, making it easier to analyze log patterns and troubleshoot issues during or after execution.

Deployment UI

• Deploy Monitors using Cavisson agent on: This section allows users to choose where the configured Log Pattern Monitors should be deployed.
• Tier: Users can select the tier on which the monitor will be deployed. The Tier dropdown displays the list of available tiers configured in the environment.
• Server : Users can choose how widely the monitor should be deployed within the selected tier. The Server dropdown allows selecting All Servers, Any Server, or a Specific Server, depending on how broadly or precisely the monitor needs to be applied.When All Servers is selected, an additional Exclude Server option becomes available, allowing users to exclude one or more servers from monitoring. Users can search and select the servers to be excluded from the list.
• Delete: This option is available only when monitors are deployed separately on multiple tiers. It allows users to remove the selected tier row from the list.
• Add Agent Tier–Server :Click the + (Add) icon in the Deployment section to define a separate Tier–Server configuration for the selected monitor.
• Add: Click Add to apply the selected Tier–Server deployment configuration. This action adds the deployment rule to the Deployment table, where the configured Tier–Server details are listed for the selected monitor.
• Open Configuration UI: Open Configuration UI: Clicking this icon redirects you to the Configured Log Pattern Monitor list screen, where you can add a new Log Pattern Monitor or edit an existing one.
• Users can download configuration settings from the clicking this option on top of the UI.

Log Pattern Deployment Table

This table displays all deployment mappings added by the user. Each row represents one deployment entry.

Explain each column point-wise:

• Tier Server Information: Shows the selected tier and server combination where the monitor will run.
• Monitors: Displays the log pattern monitor(s) mapped to that tier/server.
• Arguments: Shows any additional arguments or parameters provided for execution (if required by the monitor).
• Actions: Action: The user can perform the below operation.
  • Edit: Allows users to modify the selected deployment entry.
  • Delete: Allows users to remove the selected deployment entry.
  • Test Monitor: Allows users to validate the selected deployment configuration and verify connectivity and data collection before applying it.

Note: if no deployment entries are added, the table displays No records found.

Table Operation

• Move Column Left: Moves the selected column one position to the left in the table.
• Move Column Right: Moves the selected column one position to the right in the table.
• Insert to Left: Inserts a new column to the left of the selected column.
• Insert to Right: Inserts a new column to the right of the selected column.
• Replace Column: Replaces the selected column with another column.
• Hide Column: Hides the selected column from the table view without removing the data.
• Sorting: Allows sorting of column values either alphabetically (for text) or numerically (for numbers), helping users analyze data more efficiently.

Global Action Icons

• Delete: Removes selected deployment mappings from the Deployment table using row checkboxes. A confirmation prompt is usually shown before the entries are deleted.
• Manage Columns: Allows users to show or hide specific columns in the Deployment table to customize how deployment details are displayed.
• Column Filter: Enables filtering of deployment rows based on column values, making it easier for users to quickly find specific Tier-Server mappings or monitor assignments.