New-RedgateMonitorAlertSpecificSettings
Published 18 April 2024
Creates new Alert specific settings object for the given AlertType.
Syntax
New-RedgateMonitorAlertSpecificSettings [-AlertType] <int> [<CommonParameters>]
Description
Creates new Alert specific settings object for the given AlertType, suitable for use with Update-RedgateMonitorAlertSpecificSettings.
Parameters
-AlertType
<Int32>
The id of the alert type. Predefined ids are accessible through global alert type variables, $AlertType, $AgAlertTypes, $AzureSqlDatabaseAlertTypes, $AzureSqlServerAlertTypes, $ClusterAlertTypes, $ClusterMachineAlertTypes, $DatabaseAlertTypes, $DiskAlertTypes, $ElasticPoolAlertTypes, $InstanceAlertTypes, $JobAlertTypes and $StandaloneMachineAlertTypes.
Aliases | None |
Required? | true |
Position? | 1 |
Default Value | 0 |
Accept Pipeline Input | False |
Accept Wildcard Characters | false |
-ProgressAction
<ActionPreference>
{{ Fill ProgressAction Description }}
Aliases | None |
Required? | false |
Position? | named |
Default Value | None |
Accept Pipeline Input | False |
Accept Wildcard Characters | false |
<CommonParameters>
This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see http://technet.microsoft.com/en-us/library/hh847884.aspx.
Inputs
The input type is the type of the objects that you can pipe to the cmdlet.
-
None.
You cannot pipe input to this cmdlet.
Return values
The output type is the type of the objects that the cmdlet emits.
-
[AlertSpecificSettings] A custom sub-type of AlertSpecificSettings that's appropriate to the specified AlertType.
Examples
-------------------------- EXAMPLE 1 --------------------------
New-RedgateMonitorAlertSpecificSettings $AlertTypes.HighCpu