License usage limit approaching-f5-all
Vendor: f5
OS: all
Description:
Some licenses are limited to a certain number of elements (such as maximum users). If any of the licenses is nearing its limit, an alert will be issued.
Remediation Steps:
Consider purchasing additional licenses.
How does this work?
This alert uses the iControl REST interface to extract the compression usage.
Why is this important?
Depending on platform and license a unit may have a limit to how much HTTP compression it will handle. This metric keeps track of the usage of HTTP compression.
Without Indeni how would you find this?
Login to the device through SSH, enter TMSH and execute the command “show ltm profile http-compression global”. The row “Total” and the column “Pre-Compress” shows the aggregated bytes compressed. This would then have to be calculated by taking the delta value between two measurements and divide it by the time between the two measurements.
f5-rest-mtmgt-tm-ltm-profile-http-compression-stats
name: f5-rest-mtmgt-tm-ltm-profile-http-compression-stats
description: Determine compression usage
type: monitoring
monitoring_interval: 1 minute
requires:
vendor: f5
product: load-balancer
rest-api: 'true'
comments:
license-elements-used:
why: |
Depending on platform and license a unit may have a limit to how much HTTP compression it will handle. This metric keeps track of the usage of HTTP compression.
how: |
This alert uses the iControl REST interface to extract the compression usage.
can-with-snmp: true
can-with-syslog: false
steps:
- run:
type: HTTP
command: /mgmt/tm/ltm/profile/http-compression/stats?options=global&$select=precompressBytes,nullCompressBytes
parse:
type: JSON
file: rest-mgmt-tm-ltm-profile-http-compression-stats.parser.1.json.yaml
f5-tmsh-show-sys-license-detail-show-sys-tmm-info-global
name: f5-tmsh-show-sys-license-detail-show-sys-tmm-info-global
description: Get the TPS limit, throughput limit and compression throughput limit
type: monitoring
monitoring_interval: 5 minutes
requires:
vendor: f5
product: load-balancer
shell: bash
comments:
license-elements-limit:
why: |
License-limits can be used to regulate for instance SSL Transactions per second, APM maximum simultaneous users, maximum throughput of an F5 VE Edition or maximum compressed Mbits per second. It is important to track these whenever possible to ensure that no traffic disruption is caused by the license reaching the set threshold.
how: |
This script logs into the device through SSH and extracts the license limits.
can-with-snmp: false
can-with-syslog: false
f5-service-check:
why: |
The service check date is located in the BIG-IP license and is the same as the date the license was last activated or the date the service contract for the device expires, whichever date is earlier. This alert would serve to let the administrators know that an upgrade to the latest version is not possible without a license reactivation.
how: |
This script logs into the device through SSH and extracts the service check date. The date is then compared to the latest entry in the official F5 list located at https://support.f5.com/csp/article/K7727.
can-with-snmp: false
can-with-syslog: false
steps:
- run:
type: SSH
command: tmsh -q -c "show sys license detail;show sys tmm-info global"
parse:
type: AWK
file: tmsh-show-sys-license-show-sys-tmm-info-global.parser.1.awk
license_usage_limit
Failed to fetch the data: https://bitbucket.org/indeni/indeni-knowledge/src/master/rules/templatebased/crossvendor/license_usage_limit.scala