Kemp 360 Central is not storing ESP Extended Logs
Information
| Summary: |
Is it possible to use Kemp 360 Central as a syslog server for the extended logs? |
| Environment: |
Product: Kemp 360 Central Version: Any Platform: Virtual Application: Any |
| Question/Problem Description: |
When searching in the Global Repository within Kemp 360 Central, the ESP Extended Logs are not visible even though a packet capture confirms the logs being sent. |
| Steps to Reproduce: | |
| Error Message: | |
| Defect Number: | |
| Enhancement Number: | |
| Cause: | Log Message Retention on Ingress was set to Warn |
| Resolution: |
ESP Extended Logs are classified as Informational in syslog. So, the syslog host, in this case, Kemp 360 Central, must be configured to log at the informational level. This can be done by going to the LoadMaster's WUI > System Configuration > Logging Options > Syslog Options and make sure that the level is Informational. Next, we need to ensure that the "Log Message Retention on Ingress" option in Kemp 360 is set to Info. This determines the level of syslog logs that will be saved. This can be confirmed by going to Kemp 360 Central > Settings and Configuration > Storage > Log Message Retention on Ingress. Once completed, the logs should be visible in the Kemp 360 Central Global Repository |
| Workaround: | |
| Notes: |
https://support.kemptechnologies.com/hc/en-us/articles/6942631788685-Export-Connection-Logs |