SQL monitor database unavailable, but no alert

Luke L

Today we had an issue on the instance that hosts our SQL Monitor database.  The instance experienced about 10 minutes of downtime due to a stack dump and sql service restart.

We were not alerted by SQL monitor that this was an issue and the database and/or the entire instance was not available.  We confirmed the base monitor knew about the issue as errors were logged in that log file.

It is possible to configure Sql Monitor so that it alerts when it can't talk to it's own database?

Thanks,
-Luke.

squigley

Hello Luke,

Thanks for your inquiry with SQL Monitor.

While we do have an option to alert you if the base monitor goes down unexpectedly, unfortunately there currently isn't a way to do this for the SQL Monitor Data Repository.

I do apologize for the inconvenience that this brings.

I would highly recommend creating a request on our uservoice so that the developers can see the demand for such a feature: https://sqlmonitor.uservoice.com/forums/91743-suggestions

Please let me know if you have any other questions or concerns.

Thanks!

Luke L

Hello and thanks for your response.  It appears this feature has been requested since 2013... https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/4359531-alert-when-sql-monitor-is-having-a-problem  I just up-voted it.

The issue in the above link is exactly what we recently faced.  The SQL instance hosting the Data Repository database became unavailable, but no alerts were fired.  The instance was in an unavailable state for around 10 minutes before the cluster service was able to stop it and then bring it back online.

We would have liked to have notified that one of our mission critical instances was having trouble.

Thanks,
-Luke.

Luke L

Hello and thanks for your response.  It appears this feature has been requested since 2013... https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/4359531-alert-when-sql-monitor-is-having-a-problem  I just up-voted it.

The issue in the above link is exactly what we recently faced.  The SQL instance hosting the Data Repository database became unavailable, but no alerts were fired.  The instance was in an unavailable state for around 10 minutes before the cluster service was able to stop it and then bring it back online.

We would have liked to have notified that one of our mission critical instances was having trouble.

Thanks,
-Luke.

Luke L

Hello and thanks for your response.  It appears this feature has been requested since 2013... https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/4359531-alert-when-sql-monitor-is-having-a-problem  I just up-voted it.

The issue in the above link is exactly what we recently faced.  The SQL instance hosting the Data Repository database became unavailable, but no alerts were fired.  The instance was in an unavailable state for around 10 minutes before the cluster service was able to stop it and then bring it back online.

We would have liked to have notified that one of our mission critical instances was having trouble.

Thanks,
-Luke.

Luke L

Hello and thanks for your response.  It appears this feature has been requested since 2013... https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/4359531-alert-when-sql-monitor-is-having-a-problem  I just up-voted it.

The issue in the above link is exactly what we recently faced.  The SQL instance hosting the Data Repository database became unavailable, but no alerts were fired.  The instance was in an unavailable state for around 10 minutes before the cluster service was able to stop it and then bring it back online.

We would have liked to have notified that one of our mission critical instances was having trouble.

Thanks,
-Luke.