Setting the Http headers to be logged (csv) application metadata attribute for logging custom headers doesn't work for some APIs.
The picture below shows that customheader1 and customheader2 are set, and the expectation is that their values will be logged in Kibana. However, this logging does not work for some APIs.
Kibana shows the missing headers values for some APIs.
VIP Authentication Hub 3.3.2, 3.3.3, 3.3.4, 3.3.5
This is a known issue and will be fixed in VIP Authentication Hub 3.4
The Http headers to be logged (csv) application metadata attribute is explained in the Release Notes 3.3.2 - Fixed Issues.