# F5 Request Logging Profile is not workking **URL:** \ **Category:** Technical Forums\ **Tags:** big-ip, ltm, application-delivery\ **Created:** [October 6, 2026, 9:34am UTC](https://community.f5.com/t/f5-request-logging-profile-is-not-workking/77521 "2026-10-06T09:34:56Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Muthukumar\_Palavesam](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/muthukumar_palavesam/32/33789_2.png) [@Muthukumar\_Palavesam](https://community.f5.com/u/Muthukumar_Palavesam)\ **Post date:** [October 6, 2026, 9:34am UTC](https://community.f5.com/t/f5-request-logging-profile-is-not-workking/77521/1 "2026-10-06T09:34:56Z")
HI I need some guidance regarding an F5 BIG-IP LTM Request Logging profile configuration. Have configured a Request Logging profile on an HTTPS virtual server to send request logs to a remote syslog/logging server. However, the expected request logs are not being received / are not reaching the remote logging server. HTTPS VIP is configured with http profile assinged Verified the required ports are open in destination log server and in Firewall This log Profile is mapped with HTTPS Virtual server Log pool POOL\_HSL is configured with one logging server Conifg below ltm profile request-log LOG\_HSL { ```auto app-service none defaults-from request-log log-request-logging-errors yes proxy-close-on-error no proxy-respond-on-logging-error no proxy-response none request-log-error-pool none request-log-error-protocol mds-udp request-log-error-template none request-log-pool POOL_HSL request-log-protocol mds-udp request-log-template "$(CLIENT_IP) $(CLIENT_PORT) $(SERVER_IP) $(SERVER_PORT) $(VIRTUAL_NAME) $(HTTP_METHOD) $(HTTP_STATCODE) $(DATE_HTTP)" request-logging enabled ``` } ---
**Author:** ![Quiroman81](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/quiroman81/32/11523_2.png) [@Quiroman81](https://community.f5.com/u/Quiroman81)\ **Post date:** [October 6, 2026, 7:08pm UTC](https://community.f5.com/t/f5-request-logging-profile-is-not-workking/77521/2 "2026-10-06T19:08:51Z")
> [@Muthukumar\_Palavesam](#): > > F5 BIG-IP LTM Request Logging profile Hi Muthukumar, I have a few questions: is the remote syslog server in the same Vlan as the BIG-IP, or is it reached through a route? Could you take a packet capture to confirm whether the BIG-IP is sending the traffic? > tcpdump -ni 0.0:nnnp -s0 host and dst\_port -w /var/tmp/captura.pcap Keep in mind that HSL traffic is send from a SelfIP, so if the syslog server is reached through a route, that route must be configured in TMM (Network \> Routes), not as management route. Also, make sure the firewall rules allow the SelfIP as the source. Finally, check the status of POOL\_HSL: if the member is marked down, the BIG-IP won’t send the logs. [Configuring Request Logging](https://techdocs.f5.com/en-us/bigip-14-0-0/external-monitoring-of-big-ip-systems-implementations-14-0-0/configuring-request-logging.html) This guide is for version 14.x, but the feature hasn’t chenged much in later versions. Best regards Note I used AI to help me with the translation. Quiroman81 ---
**Author:** ![Muthukumar\_Palavesam](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/muthukumar_palavesam/32/33789_2.png) [@Muthukumar\_Palavesam](https://community.f5.com/u/Muthukumar_Palavesam)\ **Post date:** [October 7, 2026, 2:08am UTC](https://community.f5.com/t/f5-request-logging-profile-is-not-workking/77521/3 "2026-10-07T02:08:55Z")
> [@Quiroman81](#): > > take a packet capture to confirm whether the BIG-IP is sending the traffic? Thanks for the feedback .. i will check these details .. based on link shared is it mandortory to have http health monitor for the request log pool conifg ? since the request log config uses udp ---
**Author:** ![Quiroman81](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/quiroman81/32/11523_2.png) [@Quiroman81](https://community.f5.com/u/Quiroman81)\ **Post date:** [October 7, 2026, 2:26am UTC](https://community.f5.com/t/f5-request-logging-profile-is-not-workking/77521/4 "2026-10-07T02:26:56Z")
Hello Muthukimar You shouldn’t use http health monitor. For me I used in this case a ICMP health monitor. Best regards, Quiroman81 ---
**Author:** ![Muthukumar\_Palavesam](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/muthukumar_palavesam/32/33789_2.png) [@Muthukumar\_Palavesam](https://community.f5.com/u/Muthukumar_Palavesam)\ **Post date:** [October 7, 2026, 3:17am UTC](https://community.f5.com/t/f5-request-logging-profile-is-not-workking/77521/5 "2026-10-07T03:17:13Z")
> [@Quiroman81](#): > > ldn’t use http health monitor. > For me I used in this case a ICMP health monitor Thanks .. I will check these details .. Regards, Muthu ---
**Author:** ![Muthukumar\_Palavesam](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/muthukumar_palavesam/32/33789_2.png) [@Muthukumar\_Palavesam](https://community.f5.com/u/Muthukumar_Palavesam)\ **Post date:** [October 7, 2026, 5:32am UTC](https://community.f5.com/t/f5-request-logging-profile-is-not-workking/77521/6 "2026-10-07T05:32:32Z")
> [@Quiroman81](#): > > I have a few questions: is the remote syslog server in the same Vlan as the BIG-IP, or is it reached through a route? > Could you take a packet capture to confirm whether the BIG-IP is sending the traffic? HI Quiroman81, During the Wireshark analysis, we observed that HSL traffic is reaching the remote logging server, but the TCP payload contains the configured template strings rather than the expected runtime values , from the packet cpature : ![image](https://d20hrnpixdzcsd.cloudfront.net/original/3X/b/4/b46c97f55814e9b0a4bebcd97910d0dc9c7e8e86.png) Is anyhing wrong with Request Log profile config shared earlier or its due to invalid template string ? Your help would be appreciated . Regards, Muthu ---
**Author:** ![juanboticari0](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/juanboticari0/32/33673_2.png) [@juanboticari0](https://community.f5.com/u/juanboticari0)\ **Post date:** [October 7, 2026, 11:00am UTC](https://community.f5.com/t/f5-request-logging-profile-is-not-workking/77521/7 "2026-10-07T11:00:20Z")
Hello Muthukumar, I believe template variables should be enclosed in curly brackets, not parentheses. [https://my.f5.com/manage/s/article/K00847516](https://my.f5.com/manage/s/article/K00847516) Regards, Juan ---
**Author:** ![Michael\_Saleem](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/michael_saleem/32/7239_2.png) [@Michael\_Saleem](https://community.f5.com/u/Michael_Saleem)\ **Post date:** [October 7, 2026, 7:00pm UTC](https://community.f5.com/t/f5-request-logging-profile-is-not-workking/77521/8 "2026-10-07T19:00:25Z")
> [@juanboticari0](#): > > I believe template variables should be enclosed in curly brackets, not parentheses. I agree with this. Alternatively, you can just remove any brackets or parentheses e.g. $CLIENT\_IP ---
**Author:** ![Muthukumar\_Palavesam](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/muthukumar_palavesam/32/33789_2.png) [@Muthukumar\_Palavesam](https://community.f5.com/u/Muthukumar_Palavesam)\ **Post date:** [October 8, 2026, 2:01am UTC](https://community.f5.com/t/f5-request-logging-profile-is-not-workking/77521/9 "2026-10-08T02:01:23Z")
Hi Juanboticari0 Thanks . Will check these . Regards, Muthu ---
**Author:** ![Muthukumar\_Palavesam](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/muthukumar_palavesam/32/33789_2.png) [@Muthukumar\_Palavesam](https://community.f5.com/u/Muthukumar_Palavesam)\ **Post date:** [October 8, 2026, 2:02am UTC](https://community.f5.com/t/f5-request-logging-profile-is-not-workking/77521/10 "2026-10-08T02:02:04Z")
HI Michael , Sure . Thanks