-
Titolo
When do SQL Server Availability and Usability Alarms Fire? -
Descrizione
Which Foglight Cartridge for SQL Server Availability/Usability alarms will fire against certain system status? -
Causa
Below are the expected alarms to trigger when the monitored system is in a particular status.
The Foglight SQL Server agent OS extension state, if enabled or disabled will also factor in to what Availability/Usability alarms or if any alarms at all will trigger.
DBSS - Instance Availability - will fire an alarm when the instance is not available, when the service status is 'stopped'. This rule checks if the SQL Server is running, testing only the instance. This rule alerts when a SQL Server instance is not up and running. A fatal alarm will be fired. It assumes that a connection can be made to the OS and that the status of the Service can be read.
DBSS - Usability Connection Availability - will fire and alarm when the instance may be up but the agent fails to connect to it, the service status might be running but the SQL Server agent cannot open a connection against the instance, shut as when the OS has been shut down or the network connection has been blocked.
-
Risoluzione
OS monitoring disabled
OS monitoring enabled but the monitoring account does not Administrator access to query Windows services
OS monitoring enabled and the monitoring account has Local Administrator access to query Windows services
Shutdown the entire server OS - "-" printed in the Up Since
- DBSS - Usability Connection Availability alarm fires
- DBSS - Collection Status alarms fire
- Host Monitored State changed alarm fires as state is changed to UNMONITORED
- "-" printed in the Up Since
- DBSS - Usability Connection Availability alarm fires
- DBSS - Usability OS Connection Availability Alarm fires
- Credential Management alarm fires
- Host Monitored State changed alarm fires as state is changed to UNMONITORED
- "-" printed in the Up Since
- DBSS - Usability Connection Availability alarm fires
- DBSS - Usability OS Connection Availability alarm fires
- DBSS - Collection Status alarms fire
- Credential Management Event alarm fires
- Host Monitored State changed alarm fires as state is changed to UNMONITORED
Stopped the MS SQL Server Instance from object manager in SQL Server Management Studio, the MS SQL Server Agent Service is an dependency so it should stop running as well - "-" printed in the Up Since
- DBSS - Usability Connection Availability alarm fires
- DBSS Collection status alarms fire
- "-" printed in the Up Since
- DBSS - Usability Connection Availability alarm fires
- DBSS - Usability OS Connection Availability Alarm fires
- "Instance Down" printed in the Up Since
- DBSS – Instance Availability alarm triggered indicating the SQL Server instance was stopped.
Stopped the MS SQL Server Agent Service in Services No Services alarm notifications for the SQL Server Service Agent will be triggered from Foglight. The OS extension is required to monitor Services No Services alarm notifications for the SQL Server Service Agent will be triggered from Foglight. The OS extension is required to monitor Services DBSS – SQL Server agent status alarm fires
Took an individual SQL Server database offline from SQL Server management Studio DBSS – Unavailable Database alarm fires
DBSS – Unavailable Database alarm fires
DBSS – Unavailable Database alarm fires