Escalation report

tdanseytdansey
edited June 2006 in Monitoring Software v12 and lower
I just received an escalation report:



The status of xxx port 433 (xxx UK) changed to DOWN at Sat Jun 10 18:36:14 2006. Reason: Error: Could not connect to host



The problem is that today is Thursday and that is the report from a DOWN on Saturdaylast.



The rule is in fact down now, it is just that the report is an old one that never arrived on Saturday (the escalation delay is set to 15 minutes).



Any thoughts please?

Comments

  • AdministratorAdministrator
    Hard to tell what the reason is.



    Create a subdirectory of the alerts folder called

    "logs_alerts_sent"



    It will then start logging all alerts being sent (after service restart)
  • tdanseytdansey
    Will do. Thanks.
  • tdanseytdansey
    OK, the same has happened yesterday and today. The following message was received at 1.20 today and the error tripped at 11.03 but the report shows an error from a couple of Sunday's ago. What should I be looking for in the alert log folder?



    The status of ABC port 443 (xxx- xxx router)

    changed to DOWN at Sun Jun 11 20:04:44 2006.

    Reason: Error: Could not connect to host .

    dc3 1272

    test
  • AdministratorAdministrator
    Log into the online helpdesk and send the files in the folder logs_alerts_sent
This discussion has been closed.