Applies To:

Show Versions Show Versions

Manual Chapter: Health and Performance Monitoring Statistics
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Overview: Health and performance monitoring statistics

When statistics data collection is enabled, Enterprise Manager stores the following information in its statistics database for each managed device on which the Data Collection Agent is installed:

  • Specifics about the managed devices, such as host name, IP address, and software version
  • Details, such as object type and name, about any enabled network objects associated with a managed device
  • Performance and health data for managed devices and associated network objects

You can use collected statistics to display standardized reports about the health and performance of managed devices in your network. This helps you identify any systems that are not performing at full capacity and assists you in determining when you should add new devices.

Important: Enterprise Manager collects statistics only from devices that have BIG-IP Local Traffic Manager licensed and provisioned. Starting with Enterprise Manager version 2.3, Enterprise Manager can also collect statistics from devices licensed and provisioned for BIG-IP Global Traffic Manager.

To start collecting statistics, you must enable the collect statistics data feature and install the Data Collection Agent.

Enabling statistics data collection

To collect statistics you must enable data collection, which is disabled by default.
Important: Due to the processing power required to collect and store statistics data, only Enterprise Manager 4000 platform and Enterprise Manager Virtual Edition (VE) support statistics data collection. If you are upgrading from a version of Enterprise Manager that is earlier than 1.7, you must re-license the system before enabling data collection.  
Tip: If Enterprise Manager is managing devices that are part of a BIG-IP Global Traffic Manager (GTM) synchronization group, Enterprise Manager temporarily disrupts communication between GTM and remote BIG-IP objects while it verifies the version of the big3d agent on GTM. To reduce the impact to production traffic relying on the BIG-IP GTM infrastructure, we recommend that you enable statistics data collection during a maintenance window. Alternatively, you can configure the BIG-IP GTM system to maintain an available status for the virtual servers on each managed device while communication is briefly disrupted.
  1. On the Main tab, click Statistics > Options > Data Collection.
  2. For the Collect Statistics Data setting, select Enabled.
  3. Click the Save Changes button.
When you enable statistics collection, Enterprise Manager verifies that each managed device has a compatible version of the Data Collection Agent installed.

Installing the Data Collection Agent

When data collection is enabled, Enterprise Manager collects health and performance monitoring statistics data for each managed device in your network on which the most current version of the Data Collection Agent is installed. If a device on which statistics is enabled requires a more recent version of the Data Collection Agent, Enterprise Manager displays that device as Impaired in the device list, and indicates that an upgrade is required.
You can use the Data Collection Agent Installation wizard to update and install the Data Collection Agent.
  1. On the Main tab, click Enterprise Management > Tasks > Task List.
  2. Click the New Task button.
  3. For the Software Installation setting, click Install Data Collection Agent, and then click Next. The Data Collection Agent Installation screen opens.
  4. For the Device Filter setting, click the Devices with data collection enabled requiring update option. The screen refreshes to display the devices that require an update.
  5. Select the check box next to each device on which you want to install the most recent version of the Data Collection Agent, and click Next. The Task Options screen opens.
  6. From the Configuration Archive list, select an option to include or exclude private SSL keys in the configuration archive.
  7. From the Device Error Behavior list, select an option to specify how you want the system to proceed if an error occurs during the Data Collection Agent installation task.
  8. Click Next. The Task Review screen opens.
  9. In the Task Name field, you can type a new name to customize the name that displays in the task list.
  10. Click the Start Task button. The Task Properties screen opens, displaying the progress of the task. The task progress displays as Finished when the Data Collection Agent is installed.
Enterprise Manager starts collecting and storing health and performance monitoring statistics for the devices on which data collection is enabled and the Data Collection Agent is installed.

About statistics profiles

A statistics profile defines the specific performance monitoring statistics information that you want Enterprise Manager to collect, such as bytes and packets, connections, CPU utilization, memory, and disk usage. The statistics profile types correspond to the type of object that you want to monitor.

To collect performance monitoring statistics, assign one or both of these profile types, to the managed objects in your network.

Standard statistics profiles
A standard statistics profile contains all the required metrics that Enterprise Manager must collect for a specific network object type, to successfully create standard reports.
Custom statistics profiles
A custom statistics profile allows you to define your own metrics and optional threshold values for an object. By enabling or disabling data collection for certain metrics, you can prioritize the information you are collecting, ensuring that system resources are allocated appropriately.

Statistics data collected for the standard statistics profiles

When statistics collection is enabled, Enterprise Manager collects the following statistics data to create standard reports.

Report name Statistics data collected for this report
Certificate Inventory None
Device Inventory None
Capacity Planning
  • Device CPU - Processor Utilization (%)
  • Device Global Memory Utilization (%)
  • Device Global Client: Bits In (/Sec)
  • Device Global Client: Bits Out (/Sec)
Flapping Node None
Flapping Pool Member None
GTM Object Activity
  • GTM Virtual Server Bits In (Ave per Sec)
  • GTM Virtual Server Bits Out (Ave per Sec)
  • GTM Virtual Server Connections (Ave per Sec)
LTM Node Inventory None
SSL TPS Usage
  • Device Client SSL Native Connections (per Sec)
  • Device Client SSL Compat-mode Connections (per Sec)
LTM Object Activity
  • LTM Node Bits In (per Sec)
  • LTM Node Bits Out (per Sec)
  • LTM Pool Member Bits In (per Sec)
  • LTM Pool Bits In (per Sec)
  • LTM Pool Bits Out (per Sec)
  • LTM Virtual Server Bits In (per Sec)
  • LTM Virtual Server Bits Out (per Sec)
LTM Unused Object
  • LTM Node Bits In (per Sec)
  • LTM Node Bits Out (per Sec)
  • LTM Pool Member Bits In (per Sec)
  • LTM Pool Bits In (per Sec)
  • LTM Pool Bits Out (per Sec)
  • LTM Virtual Server Bits In (per Sec)
  • LTM Virtual Server Bits Out (per Sec)

Creating a custom statistics profile

Before Enterprise Manager can monitor a device, you must enable statistics collection for that device.
In most cases, a standard statistics profile is best for monitoring objects in your network. With a custom statistics profile, however, you can specify your own minimum and maximum thresholds for a number of object-specific options, providing the flexibility to specify fewer or more metrics to monitor.
  1. On the Main tab, click Statistics > Managed Devices > View.
  2. From the menu bar, select a profile type based on the type of network object for which you are creating a statistics profile.
    • Device Profiles
    • Global Traffic Profiles
    • Local Traffic Profiles
    The Profiles screen specific to that network object type opens.
  3. Click the Create button. The New Profile screen opens.
  4. From the Profile Source list, select an option.
    Option Description
    Standard Profile Select this option if you want to base the custom statistics profile on the metrics currently assigned to the standard profile for this network object type.
    None Select this option if you want to choose from all metrics available for this network object type.
    The Profile Metrics table refreshes to display the metrics associated with the source profile you selected.
  5. In the Name field, type a name for this customized profile.
  6. In the Description field, type details to help you identify this customized profile.
  7. From the Collection Interval list, select the number of seconds that you want Enterprise Manager to collect metrics.
  8. In the Profile Metrics table, select the Collect Data check box next to each metric that you want to collect.
    Important: If you selected the Standard Profile on which to base the custom statistics profile you are creating, you can select additional metrics to collect, but you must retain the current metrics for standard reports to run successfully. If you disable metrics required for standard reports, the report results will be invalid.
  9. In the metric's associated Minimum Threshold and Maximum Threshold fields, type the values the metric must reach for it to display as red in the graph. These values are optional. You are not required to specify a minimum or maximum threshold value to collect statistics for any metric.
  10. Click Save Changes.
To start using this customized statistics profile, you must assign it to specific network objects, or set it as the default for newly discovered devices.

Assigning a statistics profile to a specific device or network object

Before Enterprise Manager can monitor a device, you must enable statistics collection for that device.
Assigning a statistics profile specific to objects in your network makes it easy for you to monitor performance based on standardized settings for that object, or customized settings that you specify.
  1. On the Main tab, click Statistics > Managed Devices > View.
  2. Click the name of the device for which you want to assign a statistics profile.
  3. On the menu bar, click Statistics > Configure.
  4. Verify that the Collect Statistics Data option is set to Enabled.
  5. From the Object Type list, select the object to which you want to assign a statistics profile. The screen refreshes to display the objects for the selected object type.
  6. From the Associated Filter list, select an option to further filter the objects that you want displayed.
  7. Next to the object for which you want to assign a statistics profile, from the Associated Profile list, select a standard statistics profile or custom statistics profile for that object type.
  8. Click Save Changes.
Enterprise Manager begins to collect statistics and report performance based on the selected profile.

Specifying a default statistics profile for newly discovered devices

Before Enterprise Manager can monitor a device, the device must be enabled for statistics collection.
You can assign a default profile (either a standard statistics profile or a custom statistics profile) to start monitoring devices as soon as Enterprise Manager discovers them in your network.
  1. On the Main tab, click Statistics > Managed Devices > Device Profiles.
  2. From the Profile Name list, select the profile that you want to use as the default for any newly discovered devices.
  3. Click Save Changes.
Enterprise Manager applies the profile you selected to any newly discovered devices.

About network object statistics

With Enterprise Manager, you can easily monitor the health and activity of managed objects in your network through collected statistics. You can view activity in a summary and detailed graph format. This information ensures that your network is performing efficiently and helps you to troubleshoot potential issues. Viewing statistics provides you with an overview and details about the health and activity of the objects in your network. You can customize the information displayed in the graphics on this screen by using rule classes. This flexibility provides you the at-a-glance view, while highlighting the statistics you are most interested in.

Displaying network object statistics and customizing view

You must have statistics collection enabled for a network object for Enterprise Manager to collect and display statistics.
You can view network activity based on collected statistics in a standardized or customized format.
  1. On the Main tab, click Statistics > Managed Devices > View.
  2. From the Object Type list, select the object type for the statistics that you want to view. The screen refreshes to display the related statistics in a summary graph. If no statistics exist for the object type you selected, the Data column displays No Data.
  3. From the Rule list, select a rule class to specify the particular statistics displayed. The screen refreshes to display the associated statistics details in the summary graph.
  4. From the Time Span list, select a range of time for which to display data.
  5. Move the cursor over a graph to display a summary, or click the graph to view a detailed graph.

Rule class descriptions

The statistics data displayed is defined by the associated rule class.

Rule Class Description
All Active All statistics currently configured in the associated statistic profile
All Errors All statistics related to error conditions
Commonly Used A subset of commonly used statistics available in the associated statistic profile
Common Errors A subset of commonly occurring errors available in the associated statistic profile
Device Health A subset of device statistics related to the physical health of the device
Device Stats A subset of device statistics related to the traffic management of the device
HTTP Stats A subset of statistics related to HTTP traffic
Out of Range A collection of statistics where the value is currently exceeding a user-set threshold
Red Line A collection of resource-utilization statistics that have a user-set threshold
SSL Stats A subset of statistics related to SSL traffic
TCP Stats A subset of statistics related to TCP traffic
UDP Stats A subset of statistics related to UDP traffic

Modifying the number of records per screen to display

By default, Enterprise Manager displays up to 10 records per screen. If there are more than 10 graphs, the screen displays a link where you can view additional graphs. If you want to view more than 10 records per screen, you can increase the number displayed. This global setting affects all list screens on the Enterprise Manager system. Performance can be affected the large number of items to display on a screen.
  1. On the Main tab, click System > Preferences. The Preferences screen opens.
  2. In the Records Per Screen field, type a new value. This is a global setting and that affects all screens that lists records.
  3. Click the Update button.

About statistics storage

Enterprise Manager stores statistical data until the system reaches the storage capacity, which is by default, 1 GB stored locally. When this capacity is met, the oldest data in the system is replaced with new data, up to the storage limit. This default amount is intentionally low because when you enable statistics collection it affects the overall performance of the system. Therefore, it is important to plan for your database storage needs by understanding your system's capacity and personalize your storage requirements so you can maximize the value of the statistics features. Once you have estimated the availability of storage on your system, you can change the default database storage capacity setting. Increasing the default setting is essential to monitoring statistics data over time.

To help you plan for statistics storage, you can view the system's hard drive allocation by file type to remove any unnecessary files and calculate statistics data storage.

Viewing hard drive storage allocation

The Enterprise Manager system hard drive contains all locally-stored statistical data as well as software images, attack signature files, system logs, archives, and so forth. It is important to note that if you are collecting statistics for a large number of devices and objects, the size of the statistics database can be limited by how many other parts of the Enterprise Manager system are using the shared file system. You can view file allocation to determine if storage is maximized for your needs.
  1. In the navigation pane, click System > File System Management > File System Information.
  2. Review the storage allocation to identify any outdated or unnecessary file storage.
You can remove any superfluous files to free storage space to increase statistics data storage.

Calculating and modifying statistics storage allocation

When Enterprise Manager is configured to collect statistical data, the Data Storage screen displays a system-generated estimate of the number of days until the system reaches capacity for statistical data storage.

This number is calculated based on the current rate of data collection and the amount of disk space you specified for the storage space allocation. To retain more or less historical data, you can change the storage allocation space. To help you determine how much disk space you want to allocate to statistics storage, you can recalculate the estimated number of storage days by modifying the storage space. When you have determined that you are satisfied with the storage space value, you can then opt to save the changes.

  1. On the Main tab, click Statistics > Managed Devices > Options > Data Storage.
  2. From the Allocated Statistic Storage Space list, select a value for the number of gigabytes on the external database hard drive.
  3. Click Recalculate.
  4. Review the value displayed for the Estimated Statistics Storage Capacity With Current Settings setting.
  5. Continue to change the Allocated Statistic Storage Space value until you are satisfied with the number of days for the estimated statistics storage.
    Important: If you change the Allocated Statistic Storage Space setting to a value less than the current value, Enterprise Manager removes statistics data from the database, starting with the oldest, until it reaches the new lowered storage limit. For external databases, this value cannot exceed the available amount of disk space of the system on which you set up the external database. Enterprise Manager does not monitor the amount of disk space on the external database.
  6. Once you are satisfied with the number of days statistics are stored, click Save Changes.
Enterprise Manager allocates the specified hard drive space to statistics storage.

About statistics database backup and restoration

You can backup and restore the statistics database from the command line, or you can create a task to backup the statistics database on a regular schedule.

Scheduling statistics database backups

You must enable statistics collection and have content saved to the statistics database, before a scheduled backup can occur.
Scheduling a regular backup for you statistics database ensures you have a the option to restore it in the event of a system failure.
  1. On the Main tab, click Enterprise Manager > Tasks > Schedules > Statistics Database Backup.
  2. From the Backup Data list, select the frequency that you want Enterprise Manager to back up the statistics database. Depending on your selection, the screen refreshes to display associated options.
  3. Specify the day of the week or month, and the time of day that you want Enterprise Manager to review the device's configuration for any changes.
  4. In the Username field, type the user ID that you use to log in to the remote system.
  5. In the Hostname field, type the FQDN of the remote system.
  6. In the Path field, type the file path of the remote system.
  7. Click Save Changes.
If any changes occur during the specified time frame, Enterprise Manager backs up the statistics database.

About external storage for health and performance monitoring statistics

By default, Enterprise Manager stores health and performance monitoring statistics data in the database located on its hard drive. You have the option of configuring Enterprise Manager to store these statistics on a hard drive that is separate (external) from the Enterprise Manager system. Storing statistics on an external database clears space on Enterprise Manager for more storage of archives, images, configuration files, and so forth. A space dedicated only to health and performance monitoring statistic data can also provide you with more historical data storage.

To use an external database for health and performance monitoring statistics storage, you must create the external database and then configure Enterprise Manager to store data on that database.

If you previously collected data locally on the Enterprise Manager system, you have the option to back up and restore the data to the external database.

Task summary

Creating an external database for health and performance monitoring statistics

Storing statistics on an external database clears space on Enterprise Manager for more storage of archives, images, configuration files, and so forth. A space dedicated only to health and performance monitoring statistics can also provide you with more historical data.

You create an external database for statistics storage by issuing SQL commands on a system that is running Oracle MySQLversion 5.1 with patch 52 or later.

Important: To avoid potential time-out issues, start the MySQL instance using the --skip-name-resolve option.
  1. Access the command line of a system that is running Oracle MySQL version 5.1 with patch 52 or later. For specific information about the following commands, refer to your MySQL Reference Manual.
  2. Type: create database <database> , where <database> is the name of the external database.
  3. Type: grant all privileges on <database>.* to <username>@<host> identified by <password> , where <host> includes the IP address of the Enterprise Manager system that is storing data on the external database and <password> is the password for the user name specified.
  4. Type: grant select on mysql.proc to <username>@<host>. This command sets privileges so that the specified user can initiate the required procedures for Enterprise Manager to store and access data on the external database.
  5. Type: set global log_bin_trust_function_creators = 1. This command relaxes the privilege conditions so that Enterprise Manager can create necessary functions and procedures that enable you to store and access statistics data.
You should now edit the MySQL configuration file to optimize the database and avoid potential memory issues.

Backing up a local statistics database to an external statistics database

If you previously collected data locally on the Enterprise Manager system, you can back up and restore the local data to the external database that you created.

  1. On the Main tab, click Statistics > Managed Devices > Options > Data Collection.
  2. From the Collect Statistics Data list, select Disabled.
  3. Click the Save Changes button.
  4. On the system on which the local database is located, create a back up of the data by running the following command: mysqldump -u <user> -p -R f5em_extern> dump.sql, where <user> is the user name assigned to the database.
  5. On the system on which you created the external database, restore the data by running the following command: mysql -u <user> -p -D remotedb < dump.sql, where <user> is the user name assigned to the database.
  6. On the Main tab, click Statistics > Managed Devices > Options > Data Collection.
  7. From the Collect Statistics Data list, select Enabled.
  8. Click the Save Changes button.
You can now configure Enterprise Manager to store health and performance monitoring statistics on the external database.

Configuring Enterprise Manager to store statistics to an external database

After you have created the external database on the remote system, you can configure Enterprise Manager to store data there.

Configuring Enterprise Manager to store health and performance monitoring statistics on an external database frees system resources, and provides you with space to store statistics that is limited only by the system's hard drive on which you configure the external database.

Important: When configured to use an external database for statistics storage, Enterprise Manager no longer monitors, reports, nor sends alerts regarding storage capacity and usage, and you cannot schedule or perform statistics database backups and restorations from Enterprise Manager. When statistics are stored in an external database, the administrator of the remote system on which the statistics are stored must perform capacity management, and backup and restoration tasks independently of Enterprise Manager.

If you have two Enterprise Manager systems configured as a high availability system, configure the external database the same way on each system.

  1. On the Main tab, click Statistics > Managed Devices > Options > Data Storage.
  2. For the Statistics Data Location setting, select External. The screen refreshes to display additional fields specific to the external database option.
  3. In the External Database Address field, type the IP address of the system on which you configured the external database.
  4. In the External Database Port field, leave 3306 for the MySQL default port, or type a new port number in the field.
  5. In the External Database Name field, type a name for the external database.
  6. In the External Database User and External Database Password fields, type the credentials required to access the database.
  7. In the Allocated Statistic Storage Space field, type a value for the number of gigabytes (GB) that you want to dedicate to storing statistics. This value cannot exceed the available amount of disk space of the system on which you set up the external database. Enterprise Manager does not monitor the amount of disk space on the external database.
  8. Click Save Changes. The screen displays a summary of the configuration.
  9. If the summary details are correct, click Confirm to initialize the configuration.
When the configuration changes are fully initialized, Enterprise Manager begins to store health and performance monitoring statistics data in the external database. (This transition may take a few minutes.) Content currently stored in the local database remains there until you remove it.
Removing local statistics data storage
After you configure Enterprise Manager to store health and performance monitoring statistics on an external database location, you can remove the data stored locally to free more disk space. Before removing the local statistics, first verify that external statistics storage, data retrieval, and reporting functionality are working as expected, and that the locally-stored data is no longer useful or relevant. Or, if you want to retain the local data, back up the local data to store elsewhere, prior to deleting it.
Removing the locally-stored statistics increases the amount of storage that Enterprise Manager can use for archives, images, configuration files, and so forth.
  1. On the Main tab, click Statistics > Managed Devices > Options > Data Storage.
  2. Click the Delete Local Statistics Data button.
  3. Click Confirm.
Enterprise Manager frees the local disk space that was previously dedicated to storing statistics data.

Backing up and restoring an external statistics database

Enterprise Manager cannot run scheduled backups and restoration for statistics stored on an external database. When statistics are stored on a remote system, the administrator of must perform backup and restoration tasks independently of Enterprise Manager.

Backing up an external statistics database
You must enable statistics collection and have content saved to the configured external statistics database, before you can create a backup.
If you created an external database for health and performance monitoring statistics storage, you must manually back up that database for archive and restoration purposes.
  1. Log in to the Enterprise Manager command line as root.
  2. Type the em-backup-extern <user@host.com>:/>full_file_path_for_backup_file> command. The default file name is f5em_extern-<date stamp>.
Enterprise Manager saves the stored contents of the external statistics database to the specified file.
Restoring the external statistics database
You must backup the external statistics database before you can restore it.
If you have configured an external database on which to store statistics, and you want to restore data that you have backed up, you must do that from the command line.
  1. Log in to the Enterprise Manager command line as root.
  2. Type the em-restore-extern <user@host.com>:/>full_file_path_for_backup_file> command. For example: em-restore-extern <user@host.com>f5em_extern-<date stamp>.
Enterprise Manager restores the backed-up content of the external statistics database to the specified location.

About reports

You can use Enterprise Manager reports to retrieve and view information about the devices and BIG-IP Local Traffic Manager (LTM) and BIG-IP Global Traffic Manager (GTM) objects in your network. To create a report, you define parameters, the devices from which to collect the data, and the object types you want to include. You can collect data and view the report immediately, or you can schedule the report to run in the future either once, or at regular intervals. Depending on the report type, completed reports are presented in Adobe portable document format (PDF) or comma-separated value (CSV) text, which you can export to a spreadsheet, such as Microsoft Excel. The Capacity Planning report also supports an interactive HTML format.

Important: Before you can use the reports feature, you must enable data collection. You have the opportunity to enable data collection when you create a report. However, if you upgraded to the current version of Enterprise Manager from a version prior to 1.7, you must re-license the system before you can enable data collection. Due to the processing power required to collect and store statistical information, data collection is available only for the Enterprise Manager 4000 platform.

Standard reports

This table outlines the standard reports that you can create using Enterprise Manager.

Table 1. Enterprise Manager report descriptions
Report name Description Use this report to Format
Capacity Planning Performance capacity details about CPU usage, memory usage, and throughput To help you identify devices that are running near the edge of capacity and to make any required changes PDF and HTML
Certificate Inventory Information about the SSL certificates for the devices that Enterprise Manager has discovered in your network Easily manage multiple SSL certificates and identify those that have expired, or are about to expire CSV
Device Inventory Comprehensive details about the devices that Enterprise Manager has discovered in your network Centrally manage all of the details of the managed devices in your network CSV
Flapping LTM Node A list of Local Traffic Manager (LTM) nodes that repeatedly restart, going from an up state to a down state and back again (referred to as flapping) Identify and troubleshoot potential issues with the connectivity to nodes in your network PDF
Flapping LTM Pool Member A list of pool members that repeatedly restart, going from an up state to a down state and back again. Identify and troubleshoot potential issues with the connectively to pool members in your network PDF
GTM Object Activity Global Traffic Manager (GTM) object activity details Monitor the activity and performance of GTM objects in your network, troubleshoot potential issues, and reallocate resources as needed PDF
LTM Node Inventory The names of nodes that Enterprise Manager has discovered in your network Manage the status and state of all of the nodes in your network PDF
LTM Object Activity Local Traffic Manager (LTM) object activity details Monitor the activity and performance of LTM objects in your network, troubleshoot potential issues, and reallocate resources as needed PDF
SSL TPS Usage SSL certificate transactions per second (TPS) for each device that Enterprise Manager has discovered in your network Monitor SSL certificate activity trends for your devices, and to plan for platform upgrades and future transition to 2K bit SSL certificate keys PDF
Unused LTM Objects All Local Traffic Manager (LTM) objects that have had no activity within a configured date parameter Monitor the activity of LTM objects in your network, troubleshoot potential issues, and reallocate resources as needed PDF

Creating reports

You can create Enterprise Manager reports to easily manage details about the objects associated with the managed devices in your network.
  1. On the Main tab, click Enterprise Management > Reports. The Reports screen opens.
  2. Under Types, click the report type that you want to create. The screen refreshes, displaying any currently configured reports of the selected type that are scheduled, or have run.
  3. Click the Create button. The Report Options screen opens, displaying the settings relevant to the type of report you are creating.
  4. In the Name field, type the name as you would like it to appear on the report, and on the scheduled and completed report list.
  5. If you are creating a Certificate Inventory or Device Inventory, click the Next button and follow the steps in the Scheduling reports procedure.
  6. For the remainder of the reports, specify settings for the report, then click the Next button and then follow the steps in the Scheduling reports procedure. For specific information about each report setting, refer to the online help.

Report options

The report options vary depending on the type of report that you are creating.

You can specify values for the following settings when creating a Capacity Planning report.
Capacity Planning report setting Default value Action
Aggregation Interval No default value Specify the interval over which the data is averaged, to find the maximum capacity reached during the data collection period.
Filter N/A To restrict the number of devices displayed, type a full or partial name or IP address in the field, and click the Filter button.
Device Name No default value Select the check box next to the devices from which you want to collect data. You must select at least one device.
Memory headroom (%) 85 Specify the maximum memory threshold to use for calculating the projected date that the capacity limit is reached.
CPU headroom (%) 85 Specify the maximum CPU threshold to use for calculating the projected date that the capacity limit is reached.
Throughput headroom (bits/sec) 1000000 Specify the maximum throughput threshold to use for calculating the projected date that the capacity limit is reached.
You can specify values for the following settings when creating a Certificate Inventory report.
Flapping LTM Node report setting Default value Action
Interval (minutes) 30 Specify the period of time within which to check for flapping nodes.
Threshold (count) 2 Specify the minimum number of times during the interval that a node must flap before it is included in the report.
Filter N/A To restrict the number of devices displayed, type a full or partial name or IP address in the field, and click the Filter button.
Device Name No default value Select the check box next to the devices from which you want to collect data. You must select at least one device.
You can specify values for the following settings when creating a Flapping LTM Pool Member report.
Flapping LTM Pool Member report setting Default value Action
Interval (minutes) 30 Specify the period of time within which to check for flapping pool members.
Threshold (count) 2 Specify the minimum number of times during the interval that a pool member must flap before it is included in the report.
Filter N/A To restrict the number of devices displayed, type a full or partial name or IP address in the field, and click the Filter button.
Device Name No default value Select the check box next to the devices from which you want to collect data. You must select at least one device.
You can specify values for the following settings when creating a GTM Object Activity report.
GTM Object Activity report setting Default value Action
Max number of objects 10 Specify the maximum number of objects that you want displayed in the report.
Most or Least Active Most Active From the list, select an option to display the most active or the least active objects.
Filter N/A To restrict the number of devices displayed, type a full or partial name or IP address in the field, and click the Filter button.
Device Name No default value Select the check box next to the devices from which you want to collect data. You must select at least one device.
You can specify values for the following options when creating an LTM Node Inventory report.
LTM Node Inventory report setting Default value Action
Filter N/A To restrict the number of devices displayed, type a full or partial name or IP address in the field, and click the Filter button.
Device Name No default value Select the check box next to the devices from which you want to collect data. You must select at least one device.
You can specify values for the following settings when creating an LTM Object Activity report.
LTM Object Activity report setting Default value Action
Max number of objects 10 Specify the maximum number of objects that you want displayed in the report.
Most or Least Active Most Active From the list, select an option to display the most active or the least active objects.
Show Object All object types Clear the check box next to the object type for which you do not want to collect data.
Filter N/A To restrict the number of devices displayed, type a full or partial name or IP address in the field, and click the Filter button.
Device Name No default value Select the check box next to the devices from which you want to collect data. You must select at least one device.
You can specify values for the following options when creating an SSL TPS Usage report.
SSL TPS Usage report setting Default value Action
Filter N/A To restrict the number of devices displayed, type a full or partial name or IP address in the field, and click the Filter button.
Device Name No default value Select the check box next to the devices from which you want to collect data. You must select at least one device.
You can specify values for the following options when creating an Unused LTM Objects report.
Unused LTM Objects report setting Default value Action
Show Object All object types Clear the check box next to the object types for which you do not want to collect data.
Filter N/A To restrict the number of devices displayed, type a full or partial name or IP address in the field, and click the Filter button.
Device Name No default value Select the check box next to the device from which you want to collect data. You must select at least one device.

Scheduling reports

You must specify values for the Report Options settings before you can schedule the report.
You can schedule a report to run immediately, providing you with a current snapshot of your inventory or activity, or you can schedule the report to run in the future either once, or at regular intervals.
  1. On the Main tab, click Enterprise Management > Reports. The Reports screen opens.
  2. Under Types, click the report type that you want to schedule. The screen refreshes, displaying any currently configured reports of the selected type that are scheduled, or have run.
  3. For the Run this report setting, select an option from the list to specify when, or at what interval, to run the report. Keep in mind that frequent data collection requires more storage space, which reduces the total amount of historical data that you can keep. The settings on the screen change, depending on the option you select.
  4. If you selected an option other than Now for the Date and Time setting, specify the date and time that you want to run the report.
  5. If you are creating a Flapping Nodes, LTM Object Activity, or Unused LTM Objects report, for the Date Collection Interval setting, specify the amount of time (prior to the report run date) to collect data.
  6. To specify a person to receive this report by email, in the Email Subscription field, type the email address of the person and click Add Email.
  7. Repeat the previous step for each additional email recipient you want to add.
  8. To remove an email address, select the check box next to the email address, and click Remove.
  9. Click the Submit button to save your changes. The Reports screen opens, displaying the report in the Scheduled Reports area or the Completed Reports area, depending on when it is scheduled to run.

Viewing and downloading reports

After Enterprise Manager has collected the specified data for a report, it lists the report in the Completed Reports area of the associated Reports screen. When the report is displayed in this area, you can view it as well as can download the report for distribution or archival.
  1. On the Main tab, click Enterprise Management > Reports. The Reports screen opens.
  2. Under Types, click the report type that you want to view. The screen refreshes, displaying any currently configured reports of the selected type that are scheduled, or have run.
  3. Select the check box next to the report that you want to view, and click the Download button. You are prompted to open or save the file.
  4. Click the Open button to view the report immediately. Optionally, you can click the Save button and navigate to a place to save the file.

Viewing the interactive HTML version of the Capacity Planning report

After Enterprise Manager has gathered the specified data for a Capacity Planning report, it lists the report in the Completed Reports area. When the report is displayed in this area, you can view the interactive HTML version. When you view the HTML version of this report, you can modify the settings to instantly display updated capacity projection end dates. Alternatively, you can save the report as a static PDF file, as you do all other Enterprise Manager reports.

Note: The Capacity Planning report is the only report available in interactive HTML format.
  1. On the Main tab, click Enterprise Management > Reports. The Reports screen opens.
  2. Under Types, click Capacity Planning. The screen refreshes to display any configured Capacity Planning reports that are scheduled, or have run.
  3. Select the check box next to the Capacity Planning report that you want to view, and click the View button. The Capacity Planning report you selected displays.
  4. If you have configured this report to run for more than one device, you can select another device from the Capacity Planning for list to view the associated report.
  5. To modify the headroom for CPU, memory, or throughput metrics, type a new value in the associated Headroom field and click the Update Projection button. The report refreshes to display the updated end date projection based on the new value.
  6. To change the type of statistical analysis method, select one of the following options from the Projection Type list.
    Option Description
    No Regression Displays the usage trends for the associated metrics and does not project a run out date.
    Linear Uses the least squares linear regression analysis method, which takes into account all historical data and minimizes any deviations to calculate a projected run out date.
    Holt-Winters Uses the exponential smoothing forecasting method, which takes the most recent data more into consideration to calculate a projected run out date.

Modifying report settings

You can modify the settings for a report only if it is scheduled to run at some time in the future.
After a report is scheduled, you can change the report name, how often the report runs and, if applicable, the devices from which to collect data.
  1. On the Main tab, click Enterprise Management > Reports. The Reports screen opens.
  2. Under Types, click the report type that you want to modify. The screen refreshes, displaying any currently configured reports of the selected type that are scheduled, or have run.
  3. Select the check box next to the report that you want to modify.
  4. Click the Edit button. The Report Options screen opens.
  5. Modify the settings as required.
  6. Click the Submit button to save your changes. The Reports screen opens, displaying the report in the Scheduled Reports area or the Completed Reports area, depending on when it is scheduled to run.

Report components

The components of each report vary depending on the report type.

Capacity Planning report components

  • Device name
  • Device IP address
  • Metric (CPU, memory, throughput)
  • Peak value
  • Projected run out date range

Certificate Inventory report components

  • Device name
  • Certificate name
  • Certificate type
  • Key type
  • Version
  • Serial number
  • Certificate expiration date
  • File name
  • Bit length
  • Management mode
  • Common name
  • Certificate organization
  • Certificate division
  • Certificate country
  • Certificate state
  • Certificate locality
  • Issuer organization
  • Issuer division
  • Issuer country
  • Issuer state
  • Issuer locality

Device Inventory report components

  • Device name
  • Device IP address
  • System ID
  • Configuration utility address
  • Management port address
  • Management interface address
  • Management netmask address
  • Management gateway address
  • Enterprise Manager server IP address
  • Enterprise Manager IP address
  • Clock skew data
  • Time zone
  • Uptime (hours:minutes)
  • Platform identification
  • Serial number
  • Failover state
  • Failover mode
  • Failover forced active
  • Peer state
  • Configuration synchronization status
  • Last configuration date
  • Last configuration synchronization date
  • Last refresh date
  • User authentication URL
  • Shell access status
  • Shell access filter
  • Device location
  • Device contact information
  • Active boot (slot) location
  • Service contract end date
  • Software product
  • Software version
  • Software build number
  • Base registration key

Flapping LTM Node report components

  • Node IP address
  • Device name
  • Flap start date and time
  • Flap end date and time
  • Final state of node
  • Flap number

Flapping LTM Pool Member report components

  • Pool IP address
  • Device name
  • Flap start date and time
  • Flap end date and time
  • Final state of pool
  • Flap number

GTM Object Activity report components

  • Virtual server name
  • Device name
  • Bits per second

LTM Node Inventory report components

  • Node IP address
  • Monitor status
  • Session state
  • Ratio
  • Connection limit

LTM Object Activity report components

  • Number
  • Virtual server name
  • Device name
  • Connections per second
  • Bits per second

SSL TPS Usage report components

  • Version (product name, version, and build number)
  • Platform
  • Serial number
  • SSL per core
  • Max TPS (maximum number of recorded SSL certificate transactions per second)
  • Licensed TPS

Unused LTM Objects report components

  • Object type
  • Object name

About custom health and activity statistics queries and reports

With Enterprise Manager you can collect statistics and view details about the health and activity of the managed devices in your network. You also have the option use this collected data to create your own queries and customized graphs and reports using the details provided in the following sections in conjunction with any MySQL Connector, (available at http://dev.mysql.com/downloads/connector).

Overview of statistics types

Enterprise Manager stores in its health and performance monitoring database three types of statistics: counter statistics, gauge statistics, and threshold state statistics.

Counter statistics increment periodically to indicate a rate of change. To report the rate of change for a statistic during a specific period of time, the system performs a query for the counter statistics values and the timestamps for the beginning and end of the specified time period. Once the system receives the query response, it calculates and reports the rate of change.

Gauge statistics are absolute values for certain components, such as temperature, fan speed, and current connections. The system does not have to perform a calculation to report the absolute value of a gauge statistic.

A threshold state statistic is the current state of a specific statistic value as it relates to its threshold. That is, the threshold state indicates if the statistic value is above, below, or within a specified threshold.

Counter statistic query sample

The following SQL query example retrieves the counter statistic values for the server_pkts_in field for a node on the host device, bigip-central.

To calculate the rate of change for this example, the system compares the previous value (perfmon_node_stat p) and the current value (perfmon_node_stat c) in the perfmon_node_stat table. With this data, the system calculates the rate of change for the counter statistic using the calculation (V1-V0) / (T1-T0), where V1 is the value of the server_pkts_in field at time c.t, and V0 is the value of the server_pkts_in field at time p.t. (The insert_order field indicates the previous timestamp and value for that particular node.)

SELECT c.t, IFNULL(ABS(ROUND((p.server_pkts_in - c.server_pkts_in) / TIMESTAMPDIFF(SECOND, p.t, c.t))), 0) AS server_pkts_in_per_sec FROM perfmon_device d, perfmon_device_object o, perfmon_node_stat c, perfmon_node_stat p WHERE d.host_name = 'bigip-central' AND o.perfmon_device_uid = d.uid AND c.perfmon_device_object_uid = o.uid AND (p.insert_order = (c.insert_order – 1) AND p.perfmon_device_object_uid = c.perfmon_device_object_uid) AND c.t BETWEEN TIMESTAMPADD(MINUTE, -60, NOW()) AND NOW() AND p.t BETWEEN TIMESTAMPADD(MINUTE, -60, NOW()) AND NOW();

Gauge statistic query sample

The following example shows a gauge statistic SQL query that retrieves all values over the past hour for the chassis temperature on the host device, bigip-central.

SELECT s.t, s.temperature FROM perfmon_device d, perfmon_device_object o, perfmon_chassis_stat s WHERE d.host_name = 'bigip-central' AND o.perfmon_device_uid = d.uid AND s.perfmon_device_object_uid = o.uid AND s.t BETWEEN TIMESTAMPADD(MINUTE, -60, NOW()) AND NOW();

Threshold state statistic query sample

The following SQL query retrieves the current threshold state values for the perfmon_vip_stat.client_pkts_in field for all virtual servers associated with managed devices.

SELECT d.host_name, do.name, t.min_threshold, t.max_threshold FROM perfmon_threshold_state t, perfmon_device_object do, perfmon_device d WHERE t.perfmon_device_object_uid = do.uid AND t.stat_column_name = 'client_pkts_in' AND d.uid = do.perfmon_device_uid

About the health and performance monitoring database structure

The Enterprise Manager health and performance monitoring database consists of fact tables and dimension tables. The following diagram is an overview of the basic structure of the statistics database.

Basic structure of the statistics database

About dimension tables

Dimension tables contain object-specific details about the statistics for each managed device.

Device identification (perfmon_device)

The perfmon_device database table contains details about each managed device.

Field Type Null Value Allowed? Description
uid int unsigned NO Primary key
system_id varchar(128) NO Device identification
host_name varchar(128) NO Host name for the device
address varchar(64) NO IP address of the device
boot_location varchar(16) NO Current boot location
product_name varchar(128) NO Name of installed software
product_version varchar(64) NO Version of installed software
product_build_number varchar(32) NO Build number of installed software
ssl_total_tps int unsigned YES Licensed SSL transactions per minute
ssl_per_core varchar(16) YES Indicates if the SSL per core feature is licensed
appliance_sn varchar(64) YES Serial number of the device
platform varchar(16) YES Platform identification number
cpu_count int YES Number of CPU cores on the device

Device object identification (perfmon_device_object)

The perfmon_device_object database table contains identification details about the network objects associated with each managed device.

Field Type Null Value Allowed? Description
uid int unsigned NO Primary key
perfmon_device_uid int unsigned NO Foreign key on perfmon_device.uid
name varchar(256) NO Uniquely identifies this object
perform_object_type enum NO Type of object in the statistics table ( global,chassis,cpu,cpu_info,disk_space,udp,tcp,http,clientssl,vip,pool,pool_member,node)

About fact tables

Fact tables contain fields that are specific to the collected statistics type.

Important:

The partition_number field is not documented in the following fact tables. Do not reference the partition_number field in any custom code that you write, because that field is subject to change.

Chassis statistics (perfmon_chassis_stat)

The perfmon_chassis_stat database table contains the temperature statistics of the chassis for each managed device.

Field Type Null Value Allowed? Description Query Type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
insert_order int unsigned NO Used to calculate delta values for counter statistics N/A
t timestamp NO Time of data sample N/A
temperature int unsigned YES Temperature of chassis gauge

CPU statistics (perfmon_cpu_stat)

The perfmon_cpu_stat database table contains the temperature and fan speed statistics for each managed device.

Field Type Null Value Allowed? Description Query Type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
insert_order int unsigned NO Used to calculate delta values for counter statistics N/A
t timestamp NO Time of data sample N/A
fan_speed smallint unsigned YES Speed of CPU fan gauge
temperature int unsigned YES Temperature of CPU fan gauge

CPU usage statistics (perfmon_cpu_info_stat)

The perfmon_cpu_info_stat database table contains statistics about the CPU usage for each managed device.

Field Type Null Value Allowed? Description Query Type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
insert_order int unsigned NO Used to calculate delta values for counter statistics N/A
t timestamp NO Time of data sample N/A
cpu_usage_ratio smallint unsigned YES Ratio of CPU usage to available CPU capacity gauge

Disk space statistics (perfmon_disk_space_stat)

The perfmon_disk_space_stat database table contains details about the disk space for each managed device.

Field Type Null Value Allowed? Description Query Type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
insert_order int unsigned NO Used to calculate delta values for counter statistics. N/A
t timestamp NO Time of data sample N/A
block_size int unsigned YES Size of blocks on disk gauge
tot_blocks int unsigned YES Number of blocks on disk gauge
free_blocks int unsigned YES Number of unused blocks on disk gauge
block_ratio smallint unsigned YES Ratio of free blocks to available blocks gauge
tot_nodes int unsigned YES Number of disk nodes gauge
free_nodes int unsigned YES Number of free disk nodes gauge

GTM pool member statistics (perfmon_gtm_pool_member_stat)

The perfmon_gtm_pool_member_stat database table contains performance for each managed Global Traffic Manager (GTM) pool member.

Field Type Null Value Allowed? Description Query Type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
insert_order int unsigned NO Used to calculate delta values for counter statistics N/A
t timestamp NO Time of data sample N/A
preferred int unsigned YES Rate of requests per second successfully processed by the configured preferred load balancing method counter
alternate int unsigned YES Rate of requests per second successfully processed by the configured alternate load balancing method counter
drop int unsigned YES Rate of requests per second that were not successfully processed, and were returned to the requesting DNS server counter
fallback int unsigned YES Rate of requests per second that were successfully processed by the configured fall-back load balancing method counter

GTM pool statistics (perfmon_gtm_pool_stat)

The perfmon_gtm_pool_stat database table contains performance statistics for each managed Global Traffic Manager (GTM) pool.

Field Type Null Value Allowed? Description Query Type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
insert_order int unsigned NO Used to calculate delta values for counter statistics N/A
t timestamp NO Time of data sample N/A
preferred int unsigned YES Rate of requests per second successfully processed by the configured preferred load balancing method counter
dropped int unsigned YES Rate of requests per second that were not successfully processed, and were returned to the requesting DNS server counter
fallback int unsigned YES Rate of requests per second that were successfully processed by the configured fall-back load balancing method counter

GTM virtual server statistics (perfmon_gtm_vs_stat)

The perfmon_gtm_vs_stat database table contains performance and capacity statistics for each managed Global Traffic Manager (GTM) virtual server.

Field Type Null Value Allowed? Description Query type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
insert_order int unsigned NO Used to calculate delta values for counter statistics N/A
t timestamp NO Time of data sample N/A
cpu int unsigned YES Current amount of CPU used by this GTM virtual server gauge
mem int unsigned YES Current amount of memory used by this GTM server gauge
bits_in int unsigned YES Current amount of throughput received, measured in bits per second gauge
bits_out int unsigned YES Current amount of throughput sent, measured in bits per second gauge
conn bigint unsigned YES Current number of connections, measured per second gauge

GTM wide IP statistics (perfmon_gtm_wideip_stat)

This perfmon_gtm_wideip_stat database table contains performance statistics for each managed Global Traffic Manager (GTM) wide IP.

Field Type Null value allowed? Description Query type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
insert_order int unsigned NO Used to calculate delta values for counter statistics N/A
t timestamp NO Time of data sample N/A
preferred int unsigned YES Rate of requests per second successfully processed by the configured preferred load balancing method counter
alt int unsigned YES Rate of requests per second successfully processed by the configured alternate load balancing method counter
dropped int unsigned YES Rate of requests per second that were not successfully processed, and were returned to the requesting DNS server counter
fallback int unsigned YES Rate of requests per second that were successfully processed by the configured fall-back load balancing method counter

HTTP traffic statistics (perfmon_http_stat)

The perfmon_http_stat database table contains HTTP-related traffic statistics for each managed device.

Field Type Null Value Allowed? Description Query Type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
insert_order int unsigned NO Used to calculate delta values for counter statistics N/A
t timestamp NO Time of data sample N/A
http_cookie_persist_inserts bigint unsigned YES Rate of successful attempts to insert HTTP headers for cookie persistence (set-cookie header insertions) counter
http_resp_2xx_cnt bigint unsigned YES Rate of server-side responses in range of 200 to 206 (successful responses) counter
http_resp_3xx_cnt bigint unsigned YES Rate of server-side responses in range of 300 to 307 (redirection responses) counter
http_resp_4xx_cnt bigint unsigned YES Rate of server-side responses in range of 400 to 417 (client errors) counter
http_resp_5xx_cnt bigint unsigned YES Rate of server-side responses in range of 500 to 505 (server errors) counter
http_number_reqs bigint unsigned YES Rate of HTTP requests counter
http_get_reqs bigint unsigned YES Rate of HTTP GET requests counter
http_post_reqs bigint unsigned YES Rate of HTTP POST requests counter
http_v9_reqs bigint unsigned YES Rate of version 9 requests counter
http_v10_reqs bigint unsigned YES Rate of version 10 requests counter
http_max_keepalive_req bigint unsigned YES Maximum number of requests made in a connection gauge
http_resp_bucket_1k bigint unsigned YES Rate of responses under 1K counter
http_resp_bucket_4k bigint unsigned YES Rate of responses between 1K and 4K counter
http_resp_bucket_16k bigint unsigned YES Rate of responses between 4K and 16K counter
http_resp_bucket_32k bigint unsigned YES Rate of responses between 16K and 32K counter
http_resp_bucket_64k bigint unsigned YES This field is deprecated; use larger buckets counter
http_idle_conn_splices bigint unsigned YES Rate of response bytes before compression is applied counter
http_idle_conns bigint unsigned YES Rate of idle HTTP connections at the time of query counter
http_precompress_bytes bigint unsigned YES Rate of response bytes before compression is applied counter
http_postcompress_bytes bigint unsigned YES Rate of response bytes after compression is applied counter
http_null_compress_bytes bigint unsigned YES Rate of bytes subjected to NULL compression for license enforcement counter
http_html_precompress_bytes bigint unsigned YES Rate of bytes for HTML MIME types before compression is applied counter
http_html_postcompress_bytes bigint unsigned YES Rate of bytes for HTML MIME types after compression is applied counter
http_css_precompress_bytes bigint unsigned YES Rate of bytes for CSS MIME types before compression is applied counter
http_css_postcompress_bytes bigint unsigned YES Rate of bytes for CSS MIME types after compression is applied counter
http_js_precompress_bytes bigint unsigned YES Rate of bytes for JS MIME types before compression is applied counter
http_js_postcompress_bytes bigint unsigned YES Rate of bytes for JS MIME types after compression is applied counter
http_xml_precompress_bytes bigint unsigned YES Rate of bytes for XML MIME types before compression is applied counter
http_xml_postcompress_bytes bigint unsigned YES Rate of bytes for XML MIME types after compression is applied counter
http_sgml_precompress_bytes bigint unsigned YES Rate of bytes for SGML MIME types before compression is applied counter
http_sgml_postcompress_bytes bigint unsigned YES Rate of bytes for SGML MIME types after compression is applied counter
http_plain_precompress_bytes bigint unsigned YES Rate of bytes for plain MIME types before compression is applied counter
http_plain_postcompress_bytes bigint unsigned YES Rate of bytes for plain MIME types after compression is applied counter
http_octet_precompress_bytes bigint unsigned YES Rate of bytes for octet MIME types before compression is applied counter
http_octet_postcompress_bytes bigint unsigned YES Rate of bytes for octet MIME types after compression is applied counter
http_image_precompress_bytes bigint unsigned YES Rate of bytes for image MIME types before compression is applied counter
http_image_postcompress_bytes bigint unsigned YES Rate of bytes for image MIME types after compression is applied counter
http_video_precompress_bytes bigint unsigned YES Rate of bytes for video MIME types before compression is applied counter
http_video_postcompress_bytes bigint unsigned YES Rate of bytes for video MIME types after compression is applied counter
http_audio_precompress_bytes bigint unsigned YES Rate of bytes for audio MIME types before compression is applied counter
http_audio_postcompress_bytes bigint unsigned YES Rate of bytes for audio MIME types after compression is applied counter
http_other_precompress_bytes bigint unsigned YES Rate of bytes for other MIME types before compression is applied counter
http_other_postcompress_bytes bigint unsigned YES Rate of bytes for other MIME types after compression is applied counter
http_ramcache_hits bigint unsigned YES Rate of RAM cache hits counter
http_ramcache_misses bigint unsigned YES Rate of RAM cache misses counter
http_ramcache_misses_all bigint unsigned YES Rate of RAM cache misses, including data that could not be cached counter
http_ramcache_hit_bytes bigint unsigned YES Rate of RAM cache hits, reported in bytes counter
http_ramcache_miss_bytes bigint unsigned YES Rate of RAM cache misses, excluding data that could not be cached, reported in bytes counter
http_ramcache_miss_bytes_all bigint unsigned YES Rate of all RAM cache misses, reported in bytes counter
http_ramcache_size bigint unsigned YES Maximum available RAM cache available, reported in megabytes gauge
http_ramcache_count bigint unsigned YES Rate of items stored in RAM cache counter
http_ramcache_evictions bigint unsigned YES Rate of items removed from RAM cache to free memory for new items counter

Memory usage and connection statistics (perfmon_global_stat)

The perfmon_global_stat database table contains aggregated server-side and client-side statistics about memory usage and connections for each managed device.

Field Type Null Value Allowed? Description Query Type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
insert_order int unsigned NO Used to calculate delta values for counter statistics N/A
t timestamp NO Time of data sample N/A
client_tot_byte_in bigint unsigned YES Rate of client-side bytes received counter
client_tot_bytes_out bigint unsigned YES Rate of client-side bytes sent counter
client_pkts_in bigint unsigned YES Rate of client-side packets received counter
client_pkts_out bigint unsigned YES Rate of client-side packets sent counter
client_maxconns bigint unsigned YES Maximum number of client-side connections reported since statistics collection was set or reset for the device gauge
client_tot_conns bigint unsigned YES Rate of client-side connections per second counter
client_cur_conns bigint unsigned YES Current number of client-side connections gauge
server_tot_bytes_in bigint unsigned YES Rate of server-side bytes received counter
server_tot_bytes_out bigint unsigned YES Rate of server-side bytes sent counter
server_pkts_in bigint unsigned YES Rate of server-side packets received counter
server_pkts_out bigint unsigned YES Rate of server-side packets sent counter
server_maxconns bigint unsigned YES Maximum number of concurrent server-side connections reported since statistics collection was set or reset for the device gauge
server_cur_conns bigint unsigned YES Current number of active server-side connections gauge
server_tot_conns bigint unsigned YES Rate of server-side connections counter
mem bigint unsigned YES Available memory gauge
mem_used bigint unsigned YES Memory in use gauge
mem_ratio smallint unsigned YES Ratio of available memory to memory in use gauge
dropped bigint unsigned YES Rate of dropped packets counter
err_in bigint unsigned YES Rate of errors received counter
err_out bigint unsigned YES Rate of errors sent counter

LTM node statistics (perfmon_node_stat)

The perfmon_node_stat database table contains statistics for traffic and connections to Local Traffic Manager (LTM) node objects for each managed device.

Field Type Null value allowed? Description Query type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
insert_order int unsigned NO Used to calculate delta values for counter statistics N/A
t timestamp NO Time of data sample N/A
server_tot_bytes_in bigint unsigned YES Total number of server-side bytes received by the specified node address since statistics collection was set or reset for the device counter
server_tot_bytes_out bigint unsigned YES Rate of server-side bytes sent by the specified node address counter
server_pkts_in bigint unsigned YES Rate of server-side packets received by the specified node address counter
server_pkts_out bigint unsigned YES Rate of server-side packets sent by the specified node address counter
server_maxconns bigint unsigned YES Maximum number of concurrent server-side connections to the specified node address since statistics collection was set or reset for the device gauge
server_tot_conns bigint unsigned YES Rate of server-side connections to the specified node address counter
server_cur_conns bigint unsigned YES Current number of active server-side connections to the specified node address gauge

LTM pool member statistics (perfmon_pool_member_stat)

The perfmon_pool_member_stat database table contains traffic and connection statistics for Local Traffic Manager (LTM) pool members for each managed device.

Field Type Null Value Allowed? Description Query Type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
insert_order int unsigned NO Used to calculate delta values for counter statistics N/A
t timestamp NO Time of data sample N/A
server_tot_bytes_in bigint unsigned YES Rate of server-side bytes received by the specified pool counter
server_tot_bytes_out bigint unsigned YES Rater of server-side bytes sent by the specified pool counter
server_pkts_in bigint unsigned YES Rate of server-side packets received from the specified pool counter
server_pkts_out bigint unsigned YES Rate of server-side packets sent from the specified pool counter
server_maxconns bigint unsigned YES Maximum number of concurrent server-side connections to the specified pool reported since statistics collection was set or reset for the device gauge
server_tot_conns bigint unsigned YES Rate of server-side connections to the specified pool counter
server_cur_conns bigint unsigned YES Current number of server-side connections to the specified pool gauge

LTM pool statistics (perfmon_pool_stat)

The perfmon_pool_stat database table contains statistics for traffic and connections to Local Traffic Manager (LTM) pools for each managed device.

Field Type Null value allowed? Description Query type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
insert_order int unsigned NO Used to calculate delta values for counter statistics N/A
t timestamp NO Time of data sample N/A
server_tot_bytes_in bigint unsigned YES Rate of server-side bytes received by the specified pool counter
server_tot_bytes_out bigint unsigned YES Rate of server-side bytes sent by the specified pool counter
server_pkts_in bigint unsigned YES Rate of server-side packets received from the specified pool counter
server_pkts_out bigint unsigned YES Rate of server-side packets sent from the specified pool counter
server_maxconns bigint unsigned YES Maximum number of server-side connections to the specified pool reported since statistics collection was set or reset for the device gauge
server_tot_conns bigint unsigned YES Rate of server-side connections to the specified pool reported counter
server_cur_conns bigint unsigned YES Current number of active server-side connections to the specified pool gauge

TCP connection statistics (perfmon_tcp_stat)

The perfmon_tcp_stat database table contains TCP connection statistics for each managed device.

Field Type Null Value Allowed? Description Query Type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
insert_order int unsigned NO Used to calculate delta values for counter statistics N/A
t timestamp NO Time of data sample N/A
open int unsigned YES Rate of current open TCP connections counter
closewait int unsigned YES Rate of current TCP connections in CLOSE-WAIT/LAST-ACK state counter
finwait int unsigned YES Rate of current connections in FIN-WAIT/CLOSING state counter
timewait int unsigned YES Rate of current connections in TIME-WAIT state counter
accept bigint unsigned YES Rate of TCP connections accepted counter
acceptfails bigint unsigned YES Rate of TCP connections not accepted counter
conn bigint unsigned YES Rate of TCP connections established counter
connfail bigint unsigned YES Rate of TCP connection failures counter
expires bigint unsigned YES Rate of TCP connections that expired due to idle timeout counter
abandons bigint unsigned YES Rate of TCP connections abandoned due to retries and Keep-Alive attempts counter
rxrst bigint unsigned YES Rate of received RST packets counter
rxbadsum bigint unsigned YES Rate of bad checksum packets counter
rxbadseg bigint unsigned YES Rate of malformed segments counter
rxcookie bigint unsigned YES Rate of received SYN-cookies counter
rxbadcookie bigint unsigned YES Rate of bad SYN-cookies counter
syncacheover bigint unsigned YES Rate of SYN-cache overflow counter
txrexmits bigint unsigned YES Rate of retransmitted segments counter

Threshold state (perfmon_threshold_state)

The perfmon_threshold_state database table contains the current threshold state of each managed device.

Field Type Null Value Allowed? Description Query Type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
stat_column_name varchar(256) NO Identifies the individual statistics to which this threshold applies threshold
collection interval int unsigned NO Interval at which this statistic is collected threshold
status enum NO Status of the statistic collection (enabled,disabled, profile_change) threshold
min_threshold bigint unsigned YES Minimum value of threshold threshold
threshold_state enum NO State of the threshold range ( BELOW_MIN_THRESHOLD,ABOVE_MAX_THRESHOLD,WITHIN_THRESHOLD) threshold
threshold_exceeded_since timestamp YES Current database has exceeded threshold since this time threshold
last_alert_fired timestamp YES Time that the last alert was triggered for this out-of-threshold event threshold

UDP connection statistics (perfmon_udp_stat)

The perfmon_udp_stat database table contains UDP connection statistics for each managed device.

Field Type Null Value Allowed? Description Query Type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
insert_order int unsigned NO Used to calculate delta values for counter statistics N/A
t timestamp NO Time of data sample N/A
open int unsigned YES Rate of current open UDP connections counter
accept bigint unsigned YES Rte of accepted UDP connections counter
acceptfails bigint unsigned YES Rate of UDP connections that failed because they were not accepted counter
conn bigint unsigned YES Rate of established UDP connections counter
connfail bigint unsigned YES Rate of failed UDP connections counter
expires bigint unsigned YES Rate of expired connections due to idle timeout counter
rdxgram bigint unsigned YES Rate of datagrams received counter
rxbaddgram bigint unsigned YES Rate of malformed datagrams counter
rxunreach bigint unsigned YES Rate of received ICMP messages counter
rxnosum bigint unsigned YES Rate of UDP connections with no checksum counter
txdgram bigint unsigned YES Rate of transmitted datagram packets counter

LTM virtual server statistics (perfmon_vip_stat)

The perfmon_vip_stat database table contains statistics about the connection statistics of Local Traffic Manager (LTM) virtual servers configured for each managed device.

Field Type Null Value Allowed? Description Query Type (if applicable)
perfmon_device_object_uid int unsigned NO Used to identify the device and object as the foreign key on perfmon_device_object.uid N/A
insert_order int unsigned NO Used to calculate delta values for counter statistics N/A
t timestamp NO Time of data sample N/A
client_tot_byte_in bigint unsigned YES Rate of client-side bytes received by the specified virtual server counter
client_tot_bytes_out bigint unsigned YES Rate of client-side bytes sent from the specified virtual server counter
client_pkts_in bigint unsigned YES Rate of client-side packets received by the specified virtual server counter
client_pkts_out bigint unsigned YES Rate of client-side packets sent from the specified virtual server counter
client_maxconns bigint unsigned YES Maximum client-side connections to the specified virtual server gauge
client_tot_conns bigint unsigned YES Rate of client-side connections to the specified virtual server counter
client_cur_conns bigint unsigned YES Current number of client-side connections to the specified virtual server gauge
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)