Server(s) down-f5-all
Vendor: f5
OS: all
Description:
indeni will alert one or more servers that the load balancer is directing traffic to is down.
Remediation Steps:
Review the cause for the servers being down.
How does this work?
This alert uses the iControl REST interface to extract the node statuses on the device.
Why is this important?
A node marked as down by a monitor, or disabled by an administrator, results in reduced pool capacity or in worst case, downtime. Disabling nodes is common during ie. a maintenance window but it is easily forgotten. This metric would warn administrators when a node is not ready to accept traffic.
Without Indeni how would you find this?
Login to the device’s web interface and click on “Local Traffic” -> “Nodes”. This would show a list of the nodes and their statuses. In case the configuration is divided in multiple partitions changing to the “All [Read-only]” partition is recommended.
f5-rest-mgmt-tm-ltm-node
name: f5-rest-mgmt-tm-ltm-node
description: Determine node state and availablity
type: monitoring
monitoring_interval: 5 minutes
requires:
vendor: f5
product: load-balancer
rest-api: 'true'
comments:
lb-server-state:
why: |
A node marked as down by a monitor, or disabled by an administrator, results in reduced pool capacity or in worst case, downtime. Disabling nodes is common during ie. a maintenance window but it is easily forgotten. This metric would warn administrators when a node is not ready to accept traffic.
how: |
This alert uses the iControl REST interface to extract the node statuses on the device.
can-with-snmp: true
can-with-syslog: false
steps:
- run:
type: HTTP
command: /mgmt/tm/ltm/node?$select=fullPath,session,state
parse:
type: JSON
file: rest-mgmt-tm-ltm-node.parser.1.json.yaml
lb_server_down
Failed to fetch the data: https://bitbucket.org/indeni/indeni-knowledge/src/master/rules/templatebased/loadbalancer/lb_server_down.scala