Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Failover to log to Windows event log that failover was started / completed, and why it triggered.

Discussion in 'Ideas' started by AlexHeylin, Jan 19, 2017.

  1. AlexHeylin

    Joined:
    Nov 30, 2015
    Messages:
    44
    Likes Received:
    9
    It seems that in v15 the failover process does absolutely no logging to the Windows Event Log (which can then be picked up by 3rd party tools such as RMM). My failover scripts do extensive logging so I can see exactly what they did and when - but without 3CX logging, I can't see why the failover triggered.

    What's worse is that so far in the last two days support haven't been able to tell me one single place it does log to, so as far as I can see failover runs completely without logging of any sort. This is a feature that needs to be well documented, stable, bulletproof but above all predictable and tell you what it's doing and why. So far it's not doing well on any of those criteria.