Skip to main content
Versa Networks

Monitor Analytics Clusters

application deliver

Versa-logo-release-icon.pngFor supported software information, click here.

A Versa Analytics cluster is a set of Analytics nodes that receives raw log messages (simply called logs) from Versa Operating SystemTM (VOSTM) devices and processes them. The nodes in the cluster can store the raw logs locally or forward them to remote systems. Nodes that store logs locally can process raw logs into datastores in the cluster before archiving them. Analytics nodes provide an interface into the cluster, called the Analytics application, that allows you to configure nodes and access the information in the datastores.

The following resources are critical for Analytics nodes to function:

  • Log collector exporter program
  • Analytics driver
  • Analytics search engine
  • Analytics non-SQL (noSQL) database
  • Analytics application

These resources require the CPU, memory, and disk resources of the Analytics nodes to operate. 

For a list of operating parameters for Versa Analytics clusters, see Analytics Cluster Node Recommendations.

This article describes how to monitor Analytics resources and critical functions in Analytics clusters. This article also describes how to monitor users accessing the Analytics application.

The following table describes each Analytics resource and critical function and how to monitor them from the Director menus.

Analytics Function or Resource Description To Monitor or View

Log collector exporter program

An iteration of the log collector exporter program runs on all the Analytics log collector nodes in a cluster. This program performs the following operations for the node:

  • Process incoming log export functionality (LEF) connections containing logs.
  • Store raw logs to the local filesystem.
  • Initiate TCP, Transport Layer Security (TLS), or UDP connections to remote hosts.
  • Identify logs to stream to remote hosts using exporter rules.
  • Stream logs to remote hosts.

Monitor log collector exporter statistics:

  • Analytics > Administration > System Status > Log Collector Exporter

See Display Log Collector Exporter Status, below.

Analytics driver

All Analytics log collector nodes in a cluster run a copy of the Analytics driver. The driver performs the extract, transform, and load (ETL) operation on log files stored in /var/tmp/log. Note that the node is called a driver host.

View a snapshot of the current status of the Analytics driver:

  • Analytics > Administration > System Status > Status > General tab

See View the ETL Status, below.

 

(For Releases 22.1.1 and later.) View detailed information about the status of logs processed by the Analytics driver.

  • Analytics > Administration > System Status > Log Collector Exporter > Driver Statistics tab

Monitor usage over time for the Analytics driver:

  • Analytics > Administration > System Status > Status > ETL tab

See View the ETL Status, below.

Analytics search engine

The search engine runs on search-type Analytics nodes, where it indexes logs and performs the search function for the cluster. For a description of Analytics node types, see Analytics Cluster Node Types in Versa Analytics Configuration Concepts.

View a snapshot of the current status of search-type Analytics nodes:

  • Analytics > Administration > System Status > Status > General tab

See View the General Status of a Cluster, below.

 

Monitor the volume of logs stored in the search engine:

  • Analytics > Administration > System Status > Status > Database

See Display Datastore Status, below.

Analytics noSQL database

The noSQL database runs on analytics-type Analytics nodes, where it stores aggregated log data that is used for generating reports and populating GUI screens.

View a snapshot of the current status of analytics-type Analytics nodes:

  • Analytics > Administration > System Status > Status > General tab

See View the General Status of a Cluster, below.

 

Monitor the top 5, 10, 15, or 20 features stored in the NoSQL database:

  • Analytics > Administration > System Status > Status > Database

See Display Datastore Status, below.

Analytics application

Each node in an Analytics cluster runs an iteration of the Analytics application. This application allows you to configure and monitor Analytics nodes and view Analytics dashboards for a cluster. When you select the Analytics tab in the Director GUI, you are using the Analytics application to interact with the cluster using your Director login credentials. For more information about the Analytics application, see Versa Director Nodes and Analytics Clusters in Versa Analytics Configuration Concepts.

Monitor users currently accessing the Analytics application:

  • Analytics > Administration > System Status > Status > Database

See Display Active Users, below.

 

Monitor login and logout times for Analytics application users:

  • Analytics > Administration > Maintenance > Application Logs

See Display Analytics Application Logs, below.

CPU and memory

All critical Analytics functions use CPU and memory.

View a snapshot of current CPU and memory usage:

  • Analytics > Administration > System Status > Status > General tab

See View the General Status of a Cluster, below.

 

Monitor memory and CPU usage per node over time:

  • Analytics > Administration > System Status > Resources

See Display Disk, Memory, and CPU Usage, below.

Disk

All critical Analytics functions and cron jobs that periodically archive logs use disk storage. In general, disk storage accumulates under the following directories and their subdirectories:

  • Log storage directories, such as /var/tmp/logs
  • Log archive directories, such as /var/tmp/archives
  • NoSQL database storage directories, such as /var/lib/cassandra
  • Search engine datastore directories, such as /var/lib/solr

Note: Total disk should be at least twice that of actual storage. The extra space is required for database housekeeping (compaction) operations. If disk usage reaches 50%, disk cleanup should be performed or more storage added.

When Analytics nodes use a large percentage of their disk space, the nodes' performance may be reduced or the nodes may even become inoperable. See Troubleshoot Analytics Disk Storage Issues.

View a snapshot of current disk usage:

  • Analytics > Administration > System Status > Status > General tab

See View the General Status of a Cluster, below.

 

Monitor disk usage per node over time:

  • Analytics > Administration > System Status > Resources

See Display Disk, Memory, and CPU Usage, below.

View the General Status of a Cluster

You can display general information about a cluster, including software version information and resource usage for cluster nodes, using the Director GUI. When using the Director GUI to access Analytics information, you select a node in the Analytics cluster. The Director GUI communicates with the Analytics application running on the node, and the Analytics application relays information and instructions between the Director GUI and all nodes in the cluster. These nodes are configured as part of a connector to the Analytics cluster. For more information, see Configure an Analytics Connector in Perform Initial Software Configuration.

General Analytics cluster status includes information for search-type and analytics-type Analytics nodes. The search engine runs on search-type Analytics nodes, where it indexes logs and performs the search function for the cluster. The noSQL database runs on analytics-type Analytics nodes, where it stores aggregated log data that is used for generating reports and populating GUI screens. For a description of Analytics node types, see Analytics Cluster Node Types in Versa Analytics Configuration Concepts.

To view version information for an Analytics node:

  1. In Director view, select the Analytics tab in the top menu bar.

    Analytics_Main_Tab_Select_Node.png
  2. Hover over the Analytics tab to display a list of Analytics nodes, and then select the node.
  3. Select Administration > Version in the left menu bar. The System Version screen displays, with information for the following fields.

    Admin_Version.png
     
    Field Description
    Up Time (For Releases 20.2.3 and later.) Time elapsed since the Analytics services were last restarted.
    Package Name of the Versa Analytics software package.
    Release Date Date that the installed Versa Analytics package was released.
    Release Release number.
    Database version Version of the database running on the cluster node.
    Application ID Application identifier. The application ID is used when configuring single sign-on. See Configure Single Sign-On Using Director.

To view a snapshot of current resource usage for cluster nodes running the search engine or noSQL database:

  1. In Director view, select the Analytics tab in the top menu bar.
  2. Hover over the Analytics tab to display a list of Analytics nodes, and then select any node in the cluster.
  3. Select Administration > System Status > Status in the left menu bar. The Cluster Status table displays with the following fields.

    Cluster_Status.png
     
    Field Description
    Data Center

    Type of cluster node:

    • Analytics—Node is running the noSQL database.
    • Search—Node is running the search engine.
    Hostname Hostname or IP address of the cluster node.
    Status

    Status of the database or search engine:

    • Down
    • Up
    State

    State of the database or search engine:

    • Joining
    • Leaving
    • Moving
    • Normal
    Load

    (For Analytics data center nodes only.) Memory usage, in gibibytes (GiB).

    Disk Free Remaining disk space, in gigabytes (GB).
    Disk Used (%) Disk space used as a percentage of total disk space.
    Disk Used Disk space used, in gigabytes (GB).
    Memory Used (%) (For search data center nodes only.) Memory usage as a percentage of total memory.
    CPU Load (%) CPU usage as a percentage of total CPU.

View Database Cleanup Information

By default, Analytics nodes run cron job /etc/cron.d/vandb-auto-delete automatically each night to delete database records that have exceeded their retention time. The cron job uses retention time settings you configure from the Director GUI; see Analytics Datastore Limits in Versa Analytics Scaling Recommendations.

To view the time that the cron job was last executed:

  1. In Director view, select the Analytics tab in the top menu bar.
  2. Hover over the Analytics tab to display a list of Analytics nodes, and then select any node in the cluster.
  3. Select Administration > System Status > Status in the left menu bar.
  4. Scroll down to display the data cleanup time.

    Data_cleanup_info_on_status_tab.png

View the ETL Status

All Analytics log collector nodes in a cluster run a copy of the Analytics driver. The driver performs the extract, transform, and load (ETL) operation on log files stored in /var/tmp/log. Note that the node is called a driver host.

To display the current ETL state of driver hosts, to display detailed ETL statistics, and to start or stop the Analytics driver on a node:

  1. In Director view, select the Analytics tab in the top menu bar.
  2. Hover over the Analytics tab to display a list of Analytics nodes, and then select any node in the cluster.
  3. Select Administration > System Status > Status in the left menu bar. The following screen displays.

    Cluster_Status.png
  4. Scroll down to display the Agents & ETL Status table. The table displays the following fields.

    Agents_and_ETL_Status.png
     
    Field Description
    Hostname Hostname or IP address of the driver host.
    Status

    Status of the driver host:

    • Down
    • Up
    ETL State

    State of the Analytics driver:

    • Down
    • Running
    Uptime Elapsed time since the Analytics driver was last started.
    Actions

    Click Stop to stop the Analytics driver on the node listed in the Hostname field.

    Click Start to start the Analytics driver on the node listed in the Hostname field.

To display ETL error information and statistics over time:

  1. In the main pane, select the ETL Monitoring tab. The following charts display.

    ETL_Monitoring.png
     
    Chart Description
    ETL Errors (Group of Charts)  
    • Analytics Errors
    Cumulative number of ETL errors for analytics-type Analytics nodes in the cluster over time.
    • Processed Files
    Number of processed log files over time.
    • Search Errors
    Cumulative number of ETL errors for search-type Analytics nodes within the cluster over time.
    ETL Statistics (Group of Charts)

     

    • Pending Files
    Number of pending log files over time.
    • Memory Usage
    Memory usage of the Versa Analytics driver over time.
  2. By default, the charts are refreshed every 5 seconds. To change the chart refresh rate, select a rate from the Refresh Interval field. Options are 2, 3, 5, and 15 seconds.
  3. To change the chart style, click the Hamburger_icon.png Chart icon and select a chart type. Options are area, bar, and line chart.
  4. To view a chart in full-screen mode or to print or download a chart, click the Download_arrow_icon.png Download icon. The following menu displays. Select one of the following fields:

    Download_popup_menu.png

Display Disk, Memory, and CPU Usage

All critical Analytics functions use CPU and memory. These critical functions also use disk storage which, in general, accumulates under the following directories and their subdirectories:

  • Log storage directories, such as /var/tmp/logs
  • Log archive directories, such as /var/tmp/archives
  • NoSQL database storage directories, such as /var/lib/cassandra
  • Search engine datastore directories, such as /var/lib/solr

You can display disk, memory, and CPU usage for the cluster as a whole and for individual cluster nodes. You can display current usage and usage over time.

To display disk, CPU, and memory usage:

  1. In Director view, select the Analytics tab in the top menu bar.
  2. Hover over the Analytics tab to display a list of Analytics nodes, and then select any node in the cluster.

    Admin_SystemStatus_Resources_Menu.png
     
  3. Select Administration > System Status > Resources in the left menu bar. The Monitor Resources screen displays, showing charts for disk, memory, and CPU usage.

    Admin_SystemStatus_Resources.png
     
    Chart or Table Description
    Disk Usage Disk usage over time as a percentage of total disk.
    Memory Usage Memory usage over time in gigabytes (GB).
    CPU Load CPU usage over time as a percentage of total CPU.
    Resources Usage (Table)

    Snapshot of current resource usage.

    • Hostname
    Hostname or IP address of the Analytics node.
    • Disk Used
    Amount of disk space currently being used, in bytes.
    • Disk Used
    Amount of disk space currently being used, as a percentage of the total filesystem disk space.
    • Memory Used
    Amount of memory currently being used, as a percentage of total available memory.
    • CPU Load
    Amount of CPU currently being used as a percentage of time that the CPU is not idle.
  4. Select a time period to change the time period of the charts and table.

    System_Status_dropdown_time_period.png
     
  5. (For Releases 21.2.1 and later.) To create a custom time range, select Custom range. The Select Custom Data/Time Range window displays. Enter information for the following fields, and then click OK.

    Select_Custom_Time_Range.png
     
    Field Description
    Relative Range Click to specify a time range relative to the current time, and then enter a quantity in the first field and select a unit.
    Date Range

    Click to specify a time range between a beginning and ending time, and then enter the following:

    • In the From field, enter a beginning date and then select a beginning time.
    • In the To field, enter an ending date and then select an ending time.
    Business Hours

    (For Releases 22.1.1 and later.) Click to specify a set of business hours, and then:

    • Click individual days to indicate the days of business hours.
    • Enter the starting and ending time of business hours.

Display Datastore Status

To display the number of logs by tenant for the search engine and logs for the top ten features for the noSQL database:

  1. In Director view, select the Analytics tab in the top menu bar.
  2. Hover over the Analytics tab to display a list of Analytics nodes, and then select any node from the cluster.

    Admin_SystemStatus_Database_Menu.png
  3. Select Administration > System Status > Database in the left menu bar. The Monitor Databases screen displays the following charts and tables.

    Admin_SystemStatus_Database.png
     
    Chart or Table Name Description
    Tenants Search Logs Volume (Chart) Count of log messages sent to the search engine over time. To change the chart type, click the Hamburger_icon.png Chart icon and then select a chart type. Hover over a time or date in the chart to display details about global, provider, and tenant log counts.
    Features (Chart) Top 5, 10, 15, or 20 features present in the noSQL database. To choose the number of top features, click the Hamburger_icon.png Chart icon and then select a number. For chart types that do not display a number of hits or usage percentage, hover over the feature name to display these values.
    Tenants Search Logs Volume (Table) Count of log messages sent to the search engine.
    • Date Time
    Date and time that the log was sent.
    • Tenant
    Name of the tenant.
    • Log Count
    Number of logs sent to the search engine.
    Usage Stats (Table) Usage statistics, for the selected time period, related to the search engine and noSQL database.

Display Cluster Alarms

For Releases 21.1.3 and later.

Analytics device alarms provide real-time status about Analytics cluster resources and critical Analytics functions that require attention. The severity level associated with an alarm indicates the gravity of the situation. For an Analytics node, you can set alarm thresholds for memory, CPU, and Analytics function properties. If the node exceeds these thresholds, it generates an alarm log. Alarms are not automatically forwarded to Director nodes, so alarm information is not available for display under the Monitor tab unless you manually configure Analytics nodes to forward the alarms. You can also configure thresholds for memory and disk usage that generate an email message when a threshold is exceeded. Unlike alarms, you do not set email thresholds for individual nodes; rather, you set them for the cluster itself.

Supported Alarm Types

The following table lists the alarm types supported by Analytics nodes and the default destination for each alarm type. For a list of alarm severity levels, see Alarm Severity Levels in Configure VOS Device Alarms.

Alarm Type Description Default Destination Severity
Remote collector down Remote collector is down. syslog Critical
Remote collector queue utilization Remote collector queue utilization has exceeded the default or configured threshold value. syslog Critical, Major
System CPU utilization System CPU utilization has exceeded the default or configured threshold value. syslog Critical, Major
System disk utilization System disk utilization has exceeded the default or configured threshold value. syslog Critical, Major
System memory utilization System memory utilization has exceeded the default or configured threshold value. syslog Critical, Major
Versa Analytics driver stuck Versa Analytics Driver is not functioning. syslog Critical

Set Alarm Thresholds

You can set alarm thresholds to trigger alarm logs. You configure alarm thresholds on each node in the cluster separately.

To configure alarm thresholds:

  1. In Director view, select the Analytics tab in the top menu bar.
  2. Hover over the Analytics tab to display a list of Analytics nodes, and then select any node from the cluster.

    Admin_Config_LCE_Menu.png
  3. Select Administration > Configurations > Log Collector Exporter in the left menu bar. The Log Collector Configuration screen displays.

    LCE_Configuration_Screen.png
  4. In the Driver Hosts field, select the node to be configured.
  5. In the main pane, select the Alarm Settings tab. The following screen displays.

    2023-06-22_16-42-41.png
  6. Click Plus_sign_for_add_alarm.png Add Alarm Settings. In the Add Alarm Settings window, enter information for the following fields.
     
    Field Description
    Alarm Type

    Select an alarm type:

    • CPU Utilization
    • Disk Utilization
    • Memory Utilization
    • Remote Collector Down
    • Remote Collector Queue Utilization
    • Versa Analytics Driver Stuck
    Soak Time

    Enter how long the Analytics node waits to determine whether a condition is transient or whether it is persistent and an alarm needs to be raised.

    Range: 0 through 65535 seconds

    Low Threshold

    Enter the low threshold value as a percentage of alarm resource. Note that you cannot configure a low threshold for the Remote Collector Down and Versa Analytics Driver Stuck alarms.
    High Threshold Enter the high threshold value as a percentage of alarm resource. Note that you cannot configure a low threshold for the Remote Collector Down and Versa Analytics Driver Stuck alarms.
    Override Low Threshold Alarm Severity Select an alarm severity to override the default low-threshold alarm severity listed in Supported Alarm Types, above.
    Override High Threshold Alarm Severity Select an alarm severity to override the default high-threshold alarm severity listed in Supported Alarm Types, above.
    Disable Click to disable the alarm settings.
  7. Click Save.

Export Analytics Cluster Alarms to a Director Node

In typical configurations, you create an exporter rule to export alarm logs of all types to Director nodes. In this case, Analytics cluster alarms are included with the set of alarms and no further configuration is required. For more information about exporting alarms to Director nodes, see Export Alarm Logs to Director Nodes.

To create a separate exporter rule to stream only Analytics cluster alarms to a Director node or nodes, follow the Steps in Export Alarm Logs to Director Nodes. In Step 13, select alarm-log subtype va-alarm-log only. If you have no available local collector for Step 13, configure a dummy collector and then select it.

You can view Analytics cluster alarms from the Monitor tab in the Director GUI:

Analytics_Alarms_on_Director_Monitor_tab.png

Display Alarms

You can display alarms from the Analytics tab in the GUI and from the CLI on an Analytics node.

To display Analytics device alarms from the Analytics tab in the GUI:

  1. In Director view, select the Analytics tab in the top menu bar.
  2. Hover over the Analytics tab to display a list of Analytics nodes, and then select any node from the cluster.

    Admin_SystemStatus_Alarms_Menu.png
  3. Select Administration > System Status > Alarms in the left menu bar. The Monitor Alarms screen displays.

    Alarms_Screen.png

To display alarm logs from the CLI on an Analytics node:

  1. Log in to a shell on the Analytics node, and then start the CLI.
$ ssh 10.48.80.17 -l admin
admin@10.48.80.17's password: 
admin@Analytics$ cli
  1. Issue the show alarms command.
admin@Analytics> show alarms       
 Module    Alarm                        Time                     Text
=========  ===========================  =======================  ======================
oam        appRunning                   2021-10-07T17:47:13-0700 : versa-confd is up
oam        appRunning                   2021-10-07T17:47:13-0700 : versa-analytics-monitor is up
oam        appRunning                   2021-10-07T17:47:13-0700 : versa-lced is up
oam        appRunning                   2021-10-07T17:47:13-0700 : versa-spackmgr is up
oam        appRunning                   2021-10-07T17:47:19-0700 : versa-monit is up
oam        appRunning                   2021-10-07T17:47:19-0700 : versa-analytics-app is up
oam        appRunning                   2021-10-07T17:47:19-0700 : versa-analytics-driver is up
oam        appRunning                   2021-10-07T17:47:19-0700 : versa-analytics-dataops is up
rem-coll   remote-collector-down        2021-10-07T17:49:29-0700 Remote collector collector1 is down
system     disk-utilization             2021-10-07T17:50:26-0700 Disk utilization (97%) has crossed hard limit, system may become unusable
rem-coll   remote-collector-queue-utili 2021-10-07T19:51:49-0700 Remote collector collector1 queue has exceeded threshold value (utilization: 75%)
rem-coll   remote-collector-queue-utili 2021-10-07T20:24:26-0700 Remote collector collector1 queue near exhaustion (utilization: 94%)
system     cpu-utilization              2021-10-09T00:00:12-0700 CPU utilization (75%) has crossed a soft limit

Send Emails when Thresholds Are Exceeded

You can set resource thresholds for a cluster so that when a threshold is exceeded, the cluster automatically emails a warning to the configured email address or addresses.

To configure cluster thresholds and to automatically send email when thresholds are exceeded:

  1. In Director view, select the Analytics tab in the top menu bar.
  2. Hover over the Analytics tab to display a list of Analytics nodes, and then select any node from the cluster.

    Admin_Configuration_Settings_Menu.png
     
  3. Select Administration > System Status > Settings in the left menu bar. The Settings screen displays.

    Email_Configuration_Tab.png
  4. Select the Email Configuration tab, and then enter information for the following fields.
     
    Field Description
    SMTP Host Enter the name of the Simple Mail Transfer Protocol (SMTP) host.
    SMTP Port Enter the port number to use to connect to the SMTP host.
    Username Enter the username to use to connect to the SMTP server.
    Password Enter the password to use to connect to the SMTP server.
    SSL Click to use SSL encryption.
    TLS Click to use TLS encryption.
    Sender Email Enter the email address to place in the From: field of the email.
    System Email Notifications Enter the email address to which to send Analytics monitoring notifications. To enter more than one email address, separate them with commas.
  5. Click Save.
  6. In the main pane, select the System Monitoring tab. Enter information for the following fields.

    SystemMonitoring_Tab.png
     
    Field Description
    Enable Monitoring on this Machine Toggle On to enable monitoring of the listed thresholds. Toggle Off to disable.
    Email Notifications Toggle On to send email notifications when thresholds are exceeded. Toggle Off to disable.
    Search Disk Usage Threshold Enter a threshold value for disk usage on search-type Analytics nodes as a percentage of disk.
    Search Memory Usage Threshold Enter a threshold value for memory usage on search-type Analytics nodes as a percentage of memory.
    Analytics Disk Usage Threshold Enter a threshold value for disk usage on analytics-type Analytics nodes as a percentage of disk.
    Analytics Memory Usage Threshold Enter a threshold value for memory usage on analytics-type Analytics nodes as a percentage of memory.
    Search Logs Threshold Enter a threshold value for the number of search logs, in kilobytes.
  7. Toggle Email Notification to On.
  8. Click Save.

Display Active Users

Each node in an Analytics cluster runs an iteration of the Analytics application. This application allows you to configure and monitor Analytics nodes and view Analytics dashboards for a cluster. When you select the Analytics tab in the Director GUI, you are using the Analytics application to interact with the cluster using your Director login credentials. For more information about the Analytics application, see Versa Director Nodes and Analytics Clusters in Versa Analytics Configuration Concepts.

You can display information about users who are currently accessing the Analytics application. This includes users accessing the Analytics application from any of the following sources:

  • Analytics tab in the Director GUI
  • HTTPS connection to port 8443 on an Analytics cluster node
  • API connection to the Analytics application

To display user login and logout times, see Display Analytics Application Logs, below.

To display a list of active users currently accessing the Analytics application:

  1. In Director view, select the Analytics tab in the top menu bar.
  2. Hover over the Analytics tab to display a list of Analytics nodes, and then select any node from the cluster.

    Admin_SystemStatus_ActiveUsers_Menu.png
     
  3. Select Administration > System Status > Active Users in the left menu bar. The Active Users screen displays with the following fields.

    Active_Users_Screen.png
     

    Field

    Description

    Username

    Login name of the active user.

    Login Time

    Time that the user logged in.

    Roles

    Role of the active user. For a description of user roles, see View User Roles in Configure AAA.

    Remote Address

    IP address from which the user logged in.

Display Log Collector Exporter Status

For Releases 20.2.3 and later.

You can display statistics for the log collector exporter program running on a driver host. This program can run on multiple driver hosts in a cluster, so ensure that you select the appropriate driver host when you display statistics.

An iteration of the log collector exporter program runs on all the Analytics log collector nodes in a cluster. This program performs the following operations for the node:

  • Process incoming log export functionality (LEF) connections containing logs.
  • Store raw logs to the local filesystem.
  • Initiate TCP, TLS, or UDP connections to remote hosts.
  • Identify logs to stream to remote hosts using exporter rules.
  • Stream logs to remote hosts.

For more information about the log collector exporter, local collectors, remote collectors, and exporter rules, see Configure Log Collectors and Log Exporter Rules.

To display log collector exporter status information:

  1. In Director view, select the Analytics tab in the top menu bar.

    Analytics_Main_Tab_Select_Node.png
  2. Hover over the Analytics tab to display a list of available Analytics nodes, and then select any node in the Analytics cluster.

    Select_Admin_SystemStatus_LCE.png
     
  3. Select Administration > System Status > Log Collector Exporter in the left menu bar. The Log Collector Exporter Status screen displays.

    Admin_SystemStatus_LCE_Status.png
     
  4. In the Driver Hosts field, select an individual node to display information for only that node, or select All to display information for all nodes in the cluster. The screen displays the following information for the selected driver host or hosts.
     
    Field Description
    System Package Information (Group of Fields)  
    • Host
    Name of the driver host.
    • Package ID
    Software package ID of the Analytics image installed on the driver host.
    • Package Name
    Software package name of the Analytics image.
    • Version
    Software package version.
    • Creator
    Creator of the software package.
    • Major
    Major release number of the software package.
    • Minor
    Minor release number of the software package.
    • Service
    Service release number of the software package.
    • Release Type
    Software release type. Release types include GA (general availability).
    • Date
    Date of the software release, in the format yyyymmdd. For example, 20210910 is September 10, 2021.
    System Uptime (Group of Fields)  
    • Collector
    Name of the driver host.
    • Start Time
    Date and time that the driver host was last booted.
    • Uptime
    Time elapsed since the driver host was last booted.
  5. To display the status of connections to a driver host or hosts, select the Global Statistics tab. The following information displays.

    LCE_GlobalStatistics_tab.png
     
    Field Description

    Host

    Name of the driver host.

    Active Connections

    Number of active LEF connections.

    Clients Connected

    Number of clients connected to the driver host.
    Clients Disconnected Number of clients that have disconnected from the driver host.
    Clients Connection Error Number of connection errors.
    Clients Rejected Number of client connections rejected by the driver host.
    Client Connections Exceeds Limit Number of connections that exceeded the connection limit. For information about limiting the number of connections accepted by a local collector, see Modify or Add a Local Collector in Configure Log Collectors and Log Exporter Rules.
    Messages Received/second Number of log messages received per second.
    Messages Parsed/second Number of log messages parsed per second.
    Flow Logs Received/second Number of flow logs received per second.
    Flow Logs Received Total number of flow logs received.
    Flow Logs Throttled Total number of flow logs throttled. For information about enabling flow log throttling, see Modify or Add a Local Collector in Configure Log Collectors and Log Exporter Rules.
  1. To display statistics for local collectors configured on a driver host or hosts, select the Local Collector Statistics tab. The following information displays.

    LCE_Status_LocalCollectorStatistics_Tab.png
     
    Field Description
    eye_icon.png Eye icon Click to display detailed statistics for the local collector.
    trash_can_icon.png Clear icon Click to clear statistics for the local collector.

    Host

    Name or IP address of the driver host.

    Local Collector

    Name of the local collector.

    Connected Clients

    Number of clients connected to the local connector.
    Rejected Clients Number of client connections rejected by the local connector.
    Data Records Received Number of data records received.
    Template Records Received Number of template records received.
    Messages Received Number of log messages received.
    Message Parsing Failed Number of log messages that could not be parsed.
    Records Stored Number of records stored.
    Remote Profile Not Found Number of times a remote profile associated with the local collector was not found.
    Remove Collector Enqueue Failed Number of times the local collector failed to add an item to the queue.
  2. To display the status of local collector connections on the current driver host or hosts, select the Local Collector Connections tab. The following information displays.

    LCE_Status_LocalCollectorConnections_Tab.png
     
    Field Description
    trash_can_icon.png Clear icon Click to clear the statistics.

    Host

    Name or IP address of the driver host.

    Local Collector

    Name of the local collector on the driver host that receives the connections.
    Tenant Name of the tenant that originated the connection.
    Appliance Name of the appliance that originated the connection.
    Messages Parsed Number of incoming log messages parsed.
    Messages in Queue Number of unprocessed log messages still in the queue.
    Client Socket Client socket number.
    Client IP IP address of the return connection to the client.
    Client Port Port number of the return connection to the client.
  3. To display remote collector statistics for the current driver host or hosts, select the Remote Collector Statistics tab. The following information displays.

    LCE_Status_RemoteCollectorStatistics_Tab.png
     
    Field Description
    trash_can_icon.png Clear icon Click to clear the statistics.

    Host

    Name of the driver host.

    Remote Collector

    Name of the remote collector.
    Logs in Queue Number of logs in the queue.
    Messages Sent Number of messages sent.
    Message Send Failures Number of messages that failed to send.
    Message Size Exceeds Limit Number of messages that exceeded the message size limit.
    Message Exceeds QLimit Number of messages that exceeded the size of the queue.
  4. To display remote collector connections for the current driver host or hosts, select the Remote Collector Connections tab. The following information displays.

    LCE_Status_RemoteCollectorConnections_Tab.png
     
    Field Description
    trash_can_icon.png Clear icon Click to clear the statistics.

    Host

    Name or IP address of the driver host.
    Remote Collector Name of the remote collector.
    Server Address IP address of the remote server.
    Connection State Connection state to the remote server.
    Client Socket Socket number of the connection.
    Server Port Port number of the connection.
    Transport Type Transport type of the connection to the remote server.
    Flaps Number of times the remote collector connection changed states between up and down in a short period of time, known as a flap.
    Last Flapped Most recent time that the connection flapped.
  5. To display exporter rules for the current driver host or hosts, select the Exporter Rules tab. The following information displays.

    LCE_Status_ExporterRules_Tab.png
     
    Field Description
    trash_can_icon.png Clear icon Click to clear the statistics.

    Host

    Name or IP address of the driver host.
    Rule Name Name of the exporter rule.
    Rule Hit Count Number of times the rule has been invoked.
    Remote Collector Profile Remote collector profile used by the exporter rule.
    Local Collector Local collector used by the exporter rule.
    Tenants Number of tenants whose logs have invoked the rule.
    Log Types Log types exported by the rule.
  6. (For Releases 22.1.1 and later.) To display statistics for the Analytics driver on a node or nodes in a cluster, select the Driver Statistics tab. The following information displays.

    LCE_Status_DriverStatistics_Tab.png
     
    Field Description

    Host

    Name or IP address of the driver host.
    Analytics Errors

    Number of errors encountered with the noSQL database.

    Search Errors Number of errors encountered with the search engine.
    File Errors Number of file errors.
    Files in Queue Number of files currently in queue.
    Log Errors Number of log errors.
    Memory Usage Memory usage of driver.
    Total Logs Processed Number of logs processed.
    Analytics Queries Number of analytics queries.
    Search Queries Number of search queries.
    Processing Log Rate Rate at which logs are processed by the Analytics driver.
    Analytics Query Rate Query rate for analytics data.
    Search Query Rate Query rate for search data.
    Search Batch Query Dropped Number of times a search batch query was dropped.
    Search Queue Full Number of times the search queue was full.

     
  7. (For Releases 22.1.3 and later.) To display statistics for the events list for on a node or nodes in a cluster, select the Events List tab. An event is marked when the Versa Analytics monitor detects high resource utilization on Analytics nodes. The screen lists the event cause and a suggested action. This helps to troubleshoot Analytics resource issues quickly.

    Events_list_by_host.png
     
    Field Description

    Event Host

    Name of Analytics host where the event occurred
    Event Time Time of the event
    Event Description of the event
    Event Type Type of the event
    Event Cause Cause of the event
    Event Action Suggested action to take
    Event Details Details of the event

Display Analytics Application Logs

The Versa Analytics application runs on all nodes in an Analytics cluster. The Analytics application generates syslog messages that you can display in the Versa Director GUI. Messages are assigned syslog severity levels of error, warning, info, debug and trace, and include information about changes in Analytics alarm thresholds, Analytics database activities, and user logins and logouts.

To display Analytics application syslog messages:

  1. In Director view, select the Analytics tab in the top menu bar.
  2. Hover over the Analytics tab to display a list of Analytics nodes, and then select any node in the cluster.

    Admin_Maintenance_ApplicationLogs_Menu.png
     
  3. Select Administration > System Status > Maintenance > Application Logs in the left menu bar. The last 250 syslog messages of all severity levels display.

    Application_Log_Screen.png
     
  4. To display a specific number of rows, enter a number into the In The Last field and then click Refresh.
  5. To display logs for a specific severity level, select a value from the Level field.
     
    Severity_Level_Menu.png
     
    Field Severity Level
    All Display log messages at all syslog severity levels.
    Error Display error log messages only.
    Warning

    Display warning log messages only.

    Info Display info log messages only.
    Debug Display debug and trace log messages only.
  6. Click Refresh.

Reduce Resource Usage

The following table describes actions you can take to reduce resource usage on Analytics nodes.

Goal

Actions

Reduce the number of LEF connections

  • Use the ADC load balancer to distribute LEF connections across multiple Analytics nodes. Doing this avoids overburdening a single node in a cluster. See Configure an Application Delivery Controller.
  • Configure forwarder-type Analytics nodes, which accept LEF connections but do not run the database or search engine. This type of node reduces or redirects the task of processing incoming LEF connections away from analytics-type and search-type nodes within a cluster. See Analytics Cluster Node Types in Versa Analytics Configuration Concepts.
  • For Releases 20.2.1 and later, configure primary collectors and automatically suspend backup collectors when configuring an LEF profile. See Configure Log Export Functionality.
  • Releases 21.2.1 and later, include an Analytics node setting called Connection Eviction, which is enabled by default. This setting reduces the number of LEF connections on Analytics nodes. See New Features in Versa Analytics Release Notes for Release 21.2.

Reduce incoming log volume

Reduce datastore size

Reduce raw log storage

Reduce archive storage

Reduce resource usage
  • Unused applications or components, such as Cassandra or Tomcat, occasionally launch on log forwarders. Having them run does not affect the functionality of the Analytics node, but it does use some system resources. To disable these applications and components, run the van-lf-unused-app-cleanup.sh script.

Supported Software Information

Releases 20.2 and later support all content described in this article, except:

  • Release 20.2.3 adds the uptime field on the System Version screen; you can display status and statistics for the log collector exporter.
  • Release 21.1.3 enhances Analytics device alarm settings.
  • Release 21.2.1 adds custom time ranges for graphs.
  • Release 22.1.1 adds the Driver Statistics tab on the Log Collector Exporter Status screen; you can specify business hours in a custom date and time range.
  • Was this article helpful?