Bug ID 1017421: SASP Monitor does not log significant error conditions at default logging level

Last Modified: Apr 29, 2023

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,, 17.0.0,,

Opened: May 11, 2021

Severity: 3-Major


Most error conditions encountered by the SASP monitor are not logged at the default logging level ("error"). Most of the meaningful error conditions, including Exceptions, are logged at "info" or "debug" levels. Obtaining details to diagnose the SASP monitor issues requires reconfiguring sys db saspd.loglevel for a value of "info" or "debug".


Errors which occur intermittently or once while monitoring LTM pool members using the SASP monitor may not be diagnosable.


-- Using the SASP monitor to monitor LTM pool members -- Leaving the saspd.loglevel system DB variable configured at the default value of "error"


Configure the saspd.loglevel system DB variable with a value of "info" (for normal operations) or "debug" (if problems are occurring repeatedly).

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips