ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Some ProxySG Events Missing when logs Transferred to a Syslog Server
Article ID: 168821
Updated On:
Products
ProxySG Software - SGOS
Issue/Introduction
When checking the Syslog server, some messages are missing compared to viewing them through ProxySG Event Log.
Cause
The logs that are missing are internal ProxySG logs. Internal ProxySG logs are not sent to the syslong server. You can identify internal ProxySG logs by checking if the number 64 or 65 appears after the colon in the log, for example:
2015-10-07 07:28:10-00:00UTC "Console agent unable to respond to network request, no HTTP request data" 0 60002:65 cag_agent.cpp:440
2015-10-07 07:28:10-00:00UTC "Console agent unable to respond to network request, no HTTP request data" 0 60002:65 cag_agent.cpp:440
Resolution
Currently there is no resolution or workaround for this as this is expected behavior.
Feedback
Yes
No
Powered by
