Bug ID 748427: FPS to splunk logging is confusing

Last Modified: Jun 10, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP FPS(all modules)

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1

Opened: Nov 01, 2018
Severity: 4-Minor

Symptoms

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.

Impact

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.

Conditions

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

Workaround

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

Fix Information

None

Behavior Change