Get-LMDeviceDatasourceInstanceAlertRecipient
Syntax
Section titled “Syntax”Name-dsName
Section titled “Name-dsName”Get-LMDeviceDatasourceInstanceAlertRecipient -DatasourceName <String> -Name <String> -InstanceName <String> -DataPointName <String> [-ProgressAction <ActionPreference>] [<CommonParameters>]Id-dsName
Section titled “Id-dsName”Get-LMDeviceDatasourceInstanceAlertRecipient -DatasourceName <String> -Id <Int32> -InstanceName <String> -DataPointName <String> [-ProgressAction <ActionPreference>] [<CommonParameters>]Name-dsId
Section titled “Name-dsId”Get-LMDeviceDatasourceInstanceAlertRecipient -DatasourceId <Int32> -Name <String> -InstanceName <String> -DataPointName <String> [-ProgressAction <ActionPreference>] [<CommonParameters>]Id-dsId
Section titled “Id-dsId”Get-LMDeviceDatasourceInstanceAlertRecipient -DatasourceId <Int32> -Id <Int32> -InstanceName <String> -DataPointName <String> [-ProgressAction <ActionPreference>] [<CommonParameters>]Description
Section titled “Description”The Get-LMDeviceDatasourceInstanceAlertRecipient function retrieves the alert recipients configured for a specific data point within a device’s datasource instance. It supports identifying the device and datasource by either ID or name.
Examples
Section titled “Examples”Example 1
Section titled “Example 1”#Retrieve alert recipients using namesGet-LMDeviceDatasourceInstanceAlertRecipient -DatasourceName "Ping" -Name "Server01" -InstanceName "Instance01" -DataPointName "PingLossPercent"Example 2
Section titled “Example 2”#Retrieve alert recipients using IDsGet-LMDeviceDatasourceInstanceAlertRecipient -DatasourceId 123 -Id 456 -InstanceName "Instance01" -DataPointName "PingLossPercent"Parameters
Section titled “Parameters”-DatasourceName
Section titled “-DatasourceName”The name of the datasource. Required for Id-dsName and Name-dsName parameter sets.
Type: StringParameter Sets: Name-dsName, Id-dsNameAliases:
Required: TruePosition: NamedDefault value: NoneAccept pipeline input: FalseAccept wildcard characters: False-DatasourceId
Section titled “-DatasourceId”The ID of the datasource. Required for Id-dsId and Name-dsId parameter sets.
Type: Int32Parameter Sets: Name-dsId, Id-dsIdAliases:
Required: TruePosition: NamedDefault value: 0Accept pipeline input: FalseAccept wildcard characters: FalseThe ID of the device. Can be specified using the DeviceId alias. Required for Id-dsId and Id-dsName parameter sets.
Type: Int32Parameter Sets: Id-dsName, Id-dsIdAliases: DeviceId
Required: TruePosition: NamedDefault value: 0Accept pipeline input: FalseAccept wildcard characters: FalseThe name of the device. Can be specified using the DeviceName alias. Required for Name-dsName and Name-dsId parameter sets.
Type: StringParameter Sets: Name-dsName, Name-dsIdAliases: DeviceName
Required: TruePosition: NamedDefault value: NoneAccept pipeline input: FalseAccept wildcard characters: False-InstanceName
Section titled “-InstanceName”The name of the datasource instance. This parameter is mandatory.
Type: StringParameter Sets: (All)Aliases:
Required: TruePosition: NamedDefault value: NoneAccept pipeline input: FalseAccept wildcard characters: False-DataPointName
Section titled “-DataPointName”The name of the data point to retrieve alert recipients for. This parameter is mandatory.
Type: StringParameter Sets: (All)Aliases:
Required: TruePosition: NamedDefault value: NoneAccept pipeline input: FalseAccept wildcard characters: False-ProgressAction
Section titled “-ProgressAction”Fill ProgressAction Description
Type: ActionPreferenceParameter Sets: (All)Aliases: proga
Required: FalsePosition: NamedDefault value: NoneAccept pipeline input: FalseAccept wildcard characters: FalseCommonParameters
Section titled “CommonParameters”This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters.
Inputs
Section titled “Inputs”None. You cannot pipe objects to this command.
Section titled “None. You cannot pipe objects to this command.”Outputs
Section titled “Outputs”Returns alert recipient configuration objects.
Section titled “Returns alert recipient configuration objects.”You must run Connect-LMAccount before running this command.