This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Logs from ES1000

We recently had an email get stuck in our ES1000 that prevented all other mail from being processed.

I was wondering if there were any way for us to be able to see logs, so that in the future we could diagnose the issue and remove the offending email ourselves? We currently need to log a support call with Sophos and get them to deal with it. I can see all the mail in the queue, but I cant tell which one it gets stuck on.

This issue also didnt get picked up by the monitoring of the appliance either. We had no mail being delivered for over an hour. Is there anywhere that I can see what is actually being monitored and what the triggers are for an alert?

:332


This thread was automatically locked due to age.
Parents
  • G'day ash

    The email appliance at this point in time has SNMP alert capabilities of which it can send traps or be monitored by a suitable system.  We've published the MIB for the ESA, which you can download from the Configuration > System > Alerts & Monitoring page of the appliance GUI.

    The MIB lists the various SNMP data points of which you can monitor.

    In a direct answer to your question, we do not allow you to monitor the raw logs committed to by the appliance.  Having said that, you can export these logs at designated times and then parse them.  But this would be a re-acvtive measure.

    What would be your ideal way to monitor the logs?

    :389

    ==

    When in doubt, Script it out.

Reply
  • G'day ash

    The email appliance at this point in time has SNMP alert capabilities of which it can send traps or be monitored by a suitable system.  We've published the MIB for the ESA, which you can download from the Configuration > System > Alerts & Monitoring page of the appliance GUI.

    The MIB lists the various SNMP data points of which you can monitor.

    In a direct answer to your question, we do not allow you to monitor the raw logs committed to by the appliance.  Having said that, you can export these logs at designated times and then parse them.  But this would be a re-acvtive measure.

    What would be your ideal way to monitor the logs?

    :389

    ==

    When in doubt, Script it out.

Children
No Data