qbdbpf log file monitor service not running locally

QBDBPF LOG FILE MONITOR SERVICE NOT RUNNING LOCALLY FULL
QBDBPF LOG FILE MONITOR SERVICE NOT RUNNING LOCALLY FREE

IF – for some reason – a customer did not want to discover DB files and file groups, and ONLY wanted the total database space calculated, there is a disabled monitor targeting the DB object for the DB and one for the log file.

QBDBPF LOG FILE MONITOR SERVICE NOT RUNNING LOCALLY FREE

This is why the Base OS disk free space monitoring is still critical for SQL volumes. Now, if you DO use autogrow, and you place multiple DB files or log files on the SAME logical disk – the management pack does NOT take that into account, so your individual DB and log file monitors might not trigger because they individually are not above the threshold, but cumulatively they could fill the disk. This works EXACTLY like DB file space monitoring, except it is less complicated because there is no concept of a “filegroup” so the log file monitor rolls up to the DB object with a single dependency monitor (rollup), which is also where the alerts generate from. Everything else is designed to roll the health up correctly from DB file to File Group, and from File Group to Database object.Alerting is done at the DB File GROUP level based on a “best of” rollup.The ACTUAL space monitoring in the SQL MP is done at the individual DB file level.This rolls up to the “DB Space” monitor, which is an Aggregate rollup monitor to roll health to the DB object. Which means if ANY FILE GROUP is unhealthy, we consider the DB unhealthy. This is a rollup dependency monitor targeting the database object, and has a “worst state” rollup policy. This monitor rolls up health to the “DB File Group Space (rollup)” monitor Which is an Aggregate monitor, which has a “Worst state of any member” policy. This monitor rolls up health to “DB File Group Space” monitor. This monitor DOES generate alerts named “File Group is Running out of space” Which means if ANY child DB file has free space, then the rollup is healthy. This is a rollup dependency monitor targeting the filegroup object, and has a “best state” rollup policy. Next – all the discovered DB file monitors roll their health state up one level to the monitor “DB File Space (rollup)” The DB files will be healthy or unhealthy based on this calculation. If autogrow is not enabled, then the file size is considered the max file size and this value is used for threshold comparison.If FileMaxSize is NOT set (Unlimited) then the logical disk size is considered the upper limit.(unless logical disk size is smaller than FileMaxSize) If FileMaxSize is set – this is considered the upper limit to threshold against.If autogrow is enabled for the DB file, the script checks the DB setting for FileMaxSize to be set.

This script checks many configuration settings about the individual DB file – then rolls up a health state after complete. “$Config/ConnectionString$” “$Config/ServerName$” “$Config/SqlInstanceName$” “$Target/Host/Host/Host/Property/TcpPort$” datasource runs GetSQL2012DBFilesFreeSpace.vbs with the following parameters from the Monitor configuration: qbdbpf log file monitor service not running locally .

QBDBPF LOG FILE MONITOR SERVICE NOT RUNNING LOCALLY FULL

The reason for this is because you can have multiple files in a file group for a DB, and just having a single file being full is not an issue. This monitor does not generate alerts – it simply rolls up state.

This runs every 15 minutes, and accepts a default threshold of 10% (critical) and 20% (warning). The monitor for space is called: “ DB File Space” (.DBFileSpaceMonitor) There are unit monitors that directly target the “SQL Server 2012 DB File” class. Let’s start with free space monitoring in the DB file, this is the lowest level of monitoring. The Database > hosts > DB File Group > hosts DB File.Īlso – the Database > hosts > DB Log File. This is based on 6.6.4.0 version of the SQL MPįirst – understand the SQL MP discovers the following items:

Qbdbpf log file monitor service not running locally