by syed.hussain
I have two physical nodes in an SQL cluster, if one server is primary
the other one shows as down in the SQL service agent monitoring. Should
that not smartly know that the instance is of the same name and bypass
or show it as standby in the alert monitor.
Like (2)
Reply
Replies (7)
Would be good to understand from the developers f this is in the pipeline to be supported as not being cluster aware would mean that it would just cause issues with monitoring any clustered services.
Like (0)
Reply
Currently, we do not support this feature. However, we will have the
clusters mapped to the respective SQL servers in the first release. This
feature is in the development phase. Please follow this post for more details.
Like (0)
Reply
by Gibu Mathew
Hi Syed,
We are also contemplating on your suggestion too, to show the
status of the second one as "Standby". Now that is a new
status that we will have to introduce. It makes sense for sure.
However I have not come across anyone else having such a solution
to this problem.
Like (0)
Reply
Have there been any updates on the development of this to try and make the monitor cluster aware?
Like (0)
Reply
We are experiencing the same issue. Is this on the roadmap?
Active/Passive cluster one always shows in trouble. I would
prefer to know the cluster is correctly operational.
Like (0)
Reply
We have had the same issue too. The problem is, Site24x7 doesn't do MS SQL Cluster monitoring which it should so the passive nodes don't set off any false positive alarms. We've submitted a feature request and I've had a call with the Lead developer so hopefully this will be rolled out soon. This should not be limited to SQL server clusters either, it should be for any node clustering in Microsoft.
Like (0)
Reply
Hi,
Right now, we do not support monitoring the MSSQL in passive node. However, we are working on this feature and it will be released in any one of our future updates. Please bear with us and will update you once this feature is available.
Regards,
Rafee
Like (0)
Reply