F5 Logging left on in BigDB

This is a real life sample alert from indeni

Description:

The logging database keys have been altered more than 60 minutes ago and have not been reverted to the default settings yet. Excessive logging for long periods of time may impact performance and stability.

Altered BigDB Logging Keys:

log.arp.level (Default: Warning)
log.config.level (Default: Error)

Manual Remediation Steps:

Revert the logging settings. Review SOL13455.

How does this alert work?

indeni checks the current setting of each database key relevant to logging. The current setting is retrieved by running “tmsh show running-config sys db <key>” for each key. If the settings are changed from the known defaults, an alert is issued.

Leave a Reply