Bug ID 1710813: Tmm error logs related to per-request policies are vague/difficult to understand

Last Modified: Jan 29, 2025

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

Known Affected Versions:
16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1

Opened: Oct 29, 2024

Severity: 3-Major

Symptoms

Per-request policy error logs make it difficult to identify syntax errors EX: info tmm1[18482]: 01220002:6: Rule /Common/_sys_APM_Expression_Evaluation: syntax error in expression "[string tolower [mcget {perflow.branching.url}]] starts_with...": extra tokens at end of expression while compiling "expr {[string tolower [mcget {perflow.branching.url}]] starts_with "https://my.example.com/nweb/preregistration\" || [string tolower ..." while compiling "return [ expr {[string tolower [mcget {perflow.branching.url}]] starts_with "https://my.example.com/nweb/preregistration\" || [string..." (compiling body of proc "accessv2_proc317", line 1)

Impact

It is difficult to correct the VPE syntax using the error message report.

Conditions

-- Per-request policy configured -- A syntax error exists

Workaround

Check the corresponding ltm logs when the issue is observed.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips