if ($null-eq (Get-Command-Name'Write-IcingaForWindowsComponentCompilationFile'-ErrorAction SilentlyContinue)) {

Write-Host'['-NoNewline;

Write-Host'Error'-ForegroundColor Red-NoNewline;

Write-Host ([string]::Format(']: Failed to compile Icinga for Windows component at location "{0}", because the required function "Write-IcingaForWindowsComponentCompilationFile" is not installed. Please ensure Icinga PowerShell Framework v1.9.0 or later is installed and try again.',$MyInvocation.MyCommand.Path));

return;

}

-ScriptRootPath$PSScriptRoot`

-CompiledFilePath ($MyInvocation.MyCommand.Path);

To test thresholds with different input values, you can use the Framework Cmdlet`Get-IcingaHelpThresholds`.

Each plugin ships with a constant Framework argument`-ThresholdInterval`. This can be used to modify the value your thresholds are compared against from the current, fetched value to one collected over time by the Icinga for Windows daemon. In case you[registered service checks](https://icinga.com/docs/icinga-for-windows/latest/doc/service/10-Register-Service-Checks/) for specific time intervals, you can for example set the argument to`15m` to get the average value of 15m as base for your monitoring values. Please note that in this example, you will require to have collected the`15m` average for`Invoke-IcingaCheckCPU`.

Each plugin ships with a constant Framework argument`-ThresholdInterval`. This can be used to modify the value your thresholds are compared against from the current, fetched value to one collected over time by the Icinga for Windows daemon. In case you[Collect Metrics Over Time](https://icinga.com/docs/icinga-for-windows/latest/doc/110-Installation/06-Collect-Metrics-over-Time/) for specific time intervals, you can for example set the argument to`15m` to get the average value of 15m as base for your monitoring values. Please note that in this example, you will require to have collected the`15m` average for`Invoke-IcingaCheckCPU`.

*[Invoke-IcingaCheckMSSQLBackupStatus](plugins/01-Invoke-IcingaCheckMSSQLBackupStatus.md)

*[Invoke-IcingaCheckMSSQLHealth](plugins/02-Invoke-IcingaCheckMSSQLHealth.md)

*[Invoke-IcingaCheckMSSQLPerfCounter](plugins/03-Invoke-IcingaCheckMSSQLPerfCounter.md)

*[Invoke-IcingaCheckMSSQLResource](plugins/04-Invoke-IcingaCheckMSSQLResource.md)

| Plugin Name| Description|

| ---| ---|

|[Invoke-IcingaCheckMSSQLBackupStatus](plugins/01-Invoke-IcingaCheckMSSQLBackupStatus.md)| MSSQL plugin which checks for total backupsize, average backupsize, last backup age, last backup log age, last backup execution time, database status of a given database|

|[Invoke-IcingaCheckMSSQLHealth](plugins/02-Invoke-IcingaCheckMSSQLHealth.md)| Checks if MSSQL services for a specific instance are running and if the connection to a database instance can be established|

|[Invoke-IcingaCheckMSSQLPerfCounter](plugins/03-Invoke-IcingaCheckMSSQLPerfCounter.md)| Checks specified Performance Counter inside the MSSQL database by fetching counters by a given name and compares them to input thresholds|

|[Invoke-IcingaCheckMSSQLResource](plugins/04-Invoke-IcingaCheckMSSQLResource.md)| MSSQL plugin which checks for page life expectancy, buffer cache hit ratio', average latch wait time (ms) Performance Counters|

Released closed milestones can be found on[GitHub](https://github.com/Icinga/icinga-powershell-mssql/milestones?state=closed).

[Issue and PRs](https://github.com/Icinga/icinga-powershell-mssql/milestone/5?closed=1)

*[44](https://github.com/Icinga/icinga-powershell-mssql/pull/44) Adds support for Icinga for Windows v1.9.0 module isolation

[Issue and PRs](https://github.com/Icinga/icinga-powershell-mssql/milestone/4?closed=1)

| IntegratedSecurity| SwitchParameter| false| False| Allows this plugin to use the credentials of the current PowerShell session inherited by the user the PowerShell is running with. If this is set and the user the PowerShell is running with can access to the MSSQL database you will not require to provide username and password|

| NoPerfData| SwitchParameter| false| False| Disables the performance data output of this plugin|

| Verbosity| Object| false| 0| Changes the behavior of the plugin output which check states are printed: 0 (default): Only service checks/packages with state not OK will be printed 1: Only services with not OK will be printed including OK checks of affected check packages including Package config 2: Everything will be printed regardless of the check state 3: Identical to Verbose 2, but prints in addition the check package configuration e.g (All must be[OK])|

| ThresholdInterval|Object||| Change the value your defined threshold checks against from the current value to a collected time threshold of the Icinga for Windows daemon, as described[here](https://icinga.com/docs/icinga-for-windows/latest/doc/service/10-Register-Service-Checks/). An example for this argument would be 1m or 15m which will use the average of 1m or 15m for monitoring.|

| ThresholdInterval|String||| Change the value your defined threshold checks against from the current value to a collected time threshold of the Icinga for Windows daemon, as described[here](https://icinga.com/docs/icinga-for-windows/latest/doc/service/10-Register-Service-Checks/). An example for this argument would be 1m or 15m which will use the average of 1m or 15m for monitoring.|

| IntegratedSecurity| SwitchParameter| false| False| Allows this plugin to use the credentials of the current PowerShell session inherited by the user the PowerShell is running with. If this is set and the user the PowerShell is running with can access to the MSSQL database you will not require to provide username and password|

| NoPerfData| SwitchParameter| false| False| Disables the performance data output of this plugin|

| Verbosity| Int32| false| 0| Changes the behavior of the plugin output which check states are printed: 0 (default): Only service checks/packages with state not OK will be printed 1: Only services with not OK will be printed including OK checks of affected check packages including Package config 2: Everything will be printed regardless of the check state 3: Identical to Verbose 2, but prints in addition the check package configuration e.g (All must be[OK])|

| ThresholdInterval|Object||| Change the value your defined threshold checks against from the current value to a collected time threshold of the Icinga for Windows daemon, as described[here](https://icinga.com/docs/icinga-for-windows/latest/doc/service/10-Register-Service-Checks/). An example for this argument would be 1m or 15m which will use the average of 1m or 15m for monitoring.|

| ThresholdInterval|String||| Change the value your defined threshold checks against from the current value to a collected time threshold of the Icinga for Windows daemon, as described[here](https://icinga.com/docs/icinga-for-windows/latest/doc/service/10-Register-Service-Checks/). An example for this argument would be 1m or 15m which will use the average of 1m or 15m for monitoring.|

| IntegratedSecurity| SwitchParameter| false| False| Allows this plugin to use the credentials of the current PowerShell session inherited by the user the PowerShell is running with. If this is set and the user the PowerShell is running with can access to the MSSQL database you will not require to provide username and password|

| NoPerfData| SwitchParameter| false| False| Disables the performance data output of this plugin|

| Verbosity| Int32| false| 0| Changes the behavior of the plugin output which check states are printed: 0 (default): Only service checks/packages with state not OK will be printed 1: Only services with not OK will be printed including OK checks of affected check packages including Package config 2: Everything will be printed regardless of the check state 3: Identical to Verbose 2, but prints in addition the check package configuration e.g (All must be[OK])|

| ThresholdInterval|Object||| Change the value your defined threshold checks against from the current value to a collected time threshold of the Icinga for Windows daemon, as described[here](https://icinga.com/docs/icinga-for-windows/latest/doc/service/10-Register-Service-Checks/). An example for this argument would be 1m or 15m which will use the average of 1m or 15m for monitoring.|

| ThresholdInterval|String||| Change the value your defined threshold checks against from the current value to a collected time threshold of the Icinga for Windows daemon, as described[here](https://icinga.com/docs/icinga-for-windows/latest/doc/service/10-Register-Service-Checks/). An example for this argument would be 1m or 15m which will use the average of 1m or 15m for monitoring.|

| IntegratedSecurity| SwitchParameter| false| False| Allows this plugin to use the credentials of the current PowerShell session inherited by the user the PowerShell is running with. If this is set and the user the PowerShell is running with can access to the MSSQL database you will not require to provide username and password|

| NoPerfData| SwitchParameter| false| False| Disables the performance data output of this plugin|

| Verbosity| Int32| false| 0| Changes the behavior of the plugin output which check states are printed: 0 (default): Only service checks/packages with state not OK will be printed 1: Only services with not OK will be printed including OK checks of affected check packages including Package config 2: Everything will be printed regardless of the check state 3: Identical to Verbose 2, but prints in addition the check package configuration e.g (All must be[OK])e|

| ThresholdInterval|Object||| Change the value your defined threshold checks against from the current value to a collected time threshold of the Icinga for Windows daemon, as described[here](https://icinga.com/docs/icinga-for-windows/latest/doc/service/10-Register-Service-Checks/). An example for this argument would be 1m or 15m which will use the average of 1m or 15m for monitoring.|

| ThresholdInterval|String||| Change the value your defined threshold checks against from the current value to a collected time threshold of the Icinga for Windows daemon, as described[here](https://icinga.com/docs/icinga-for-windows/latest/doc/service/10-Register-Service-Checks/). An example for this argument would be 1m or 15m which will use the average of 1m or 15m for monitoring.|

RequiredModules=@(

@{ModuleName='icinga-powershell-framework';ModuleVersion='1.5.0' },

@{ModuleName='icinga-powershell-framework';ModuleVersion='1.9.0' },

@{ModuleName='icinga-powershell-plugins';ModuleVersion='1.5.0' }

)

NestedModules=@(

)

FunctionsToExport=@(

)

CmdletsToExport=@(

)

VariablesToExport=@(

)

FunctionsToExport=@('*')

CmdletsToExport=@('*')

AliasesToExport=@()

PrivateData=@{

PSData=@{

Tags=@('icinga','icinga2','mssqlplugins','icingamssql','icinga2mssql','icingawindows')

}

}

functionImport-IcingaPowerShellComponentMSSQL()

{

}

Export-ModuleMember-Variable@('MSSQLProviderEnums');