Forum Discussion

Stefan_Klotz's avatar
Stefan_Klotz
Icon for Cumulonimbus rankCumulonimbus
Apr 30, 2025

Change severity for sod log messages

I need to change the severity for some log messages from the sod service. The ones I'm looking for are currently issued with severity notice and I want to increase this to warning. I already found ...
log
Jmtaylor's avatar
Jmtaylor
Icon for Moderator rankModerator
Oct 10, 2025

Stefan_Klotz​  

 

I was able to dig up  some information for your question Stefan. I  used AI to format the information 

Based on the available F5 documentation, it is not possible to change the severity of SOD (Switchover Daemon) log messages from "notice" to "warning" using a database variable or by editing a mapping file in a way that is persistent and supported.

Key points from the documentation:

  • According to KB K000150405: F5OS-A The priority and severity of a log message are not the same, the log level (priority) and alarm severity are different and are not 1-to-1 mapped. The log message's priority (e.g., "notice") is not directly controlled by a user-accessible setting, and there is no supported method to remap these for SOD logs. The article explicitly states there are no recommended actions for changing this behavior.
    Source: K000150405 F5OS-A The priority and severity of a log message are not the same
  • There is no mention in the official documentation or CLI guides of a supported, persistent, or upgrade-safe method to change the severity of SOD log messages. Editing internal mapping files is not supported and may be overwritten by upgrades or reboots.
  • The "remote logging severity attribute" (see KB K9577) only applies to ASM remote logging profiles and does not affect local log message severity or SOD logs.
    Source: Legacy Content K9577 The remote logging severity attribute
  • No db variables exist for SOD log severity, as you have already discovered.

In summary:
There is no supported, persistent, or upgrade-safe method to change the severity of SOD log messages from "notice" to "warning." Any changes made to internal files are likely to be reverted by system updates or reboots, and are not recommended or supported by F5.

If you have a specific operational or compliance requirement, you may consider filtering or reclassifying these messages at your log aggregation/monitoring system (e.g., syslog server, SIEM) rather than on the F5 device itself.

If you need further assistance or have a specific use case, please provide more details.

References: