Bug ID 748427: FPS to splunk logging is confusing

Last Modified: Sep 13, 2023

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

Known Affected Versions:
13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,

Opened: Nov 01, 2018

Severity: 4-Minor


When using a splunk destination for the risk-engine publisher, the log message template is ignored. instead all available fields are logged in a splunk formatted way. On the other hand, FPS requires a non-empty log message for actually sending the logs, this means that the user must assign a dummy value in the log message template.


User must set a dummy content for the log messages in order to be able to send the logs. However, the actual content will be not as expected in case of a splunk formatted destination.


1. splunk destination 2. non empty log message (sys db antifraud.internalconfig.strin1 or antifraud.internalconfig.strin2)


Set a dummy value (a single space will do) in the log messages template.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips