Get-AzDiagnosticSettingCategory
Gets the diagnostic settings category for the specified resource.
Syntax
Get-AzDiagnosticSettingCategory
-ResourceId <String>
[-DefaultProfile <PSObject>]
[<CommonParameters>]
Get-AzDiagnosticSettingCategory
-Name <String>
-ResourceId <String>
[-DefaultProfile <PSObject>]
[<CommonParameters>]
Get-AzDiagnosticSettingCategory
-InputObject <IDiagnosticSettingIdentity>
[-DefaultProfile <PSObject>]
[<CommonParameters>]
Description
Gets the diagnostic settings category for the specified resource.
Examples
Example 1: List supported diagnostic setting categories
$subscriptionId = (Get-AzContext).Subscription.Id
Get-AzDiagnosticSettingCategory -ResourceId /subscriptions/$subscriptionId/resourceGroups/test-rg-name/providers/Microsoft.AppPlatform/Spring/springcloud-001
List supported diagnostic setting categories for resource
Parameters
-DefaultProfile
The DefaultProfile parameter is not functional. Use the SubscriptionId parameter when available if executing the cmdlet against a different subscription.
Type: | PSObject |
Aliases: | AzureRMContext, AzureCredential |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-InputObject
Identity Parameter To construct, see NOTES section for INPUTOBJECT properties and create a hash table.
Type: | IDiagnosticSettingIdentity |
Position: | Named |
Default value: | None |
Required: | True |
Accept pipeline input: | True |
Accept wildcard characters: | False |
-Name
The name of the diagnostic setting.
Type: | String |
Position: | Named |
Default value: | None |
Required: | True |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-ResourceId
The identifier of the resource.
Type: | String |
Position: | Named |
Default value: | None |
Required: | True |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Inputs
Outputs
Commentaires
https://aka.ms/ContentUserFeedback.
Bientôt disponible : Tout au long de 2024, nous allons supprimer progressivement GitHub Issues comme mécanisme de commentaires pour le contenu et le remplacer par un nouveau système de commentaires. Pour plus d’informations, consultezEnvoyer et afficher des commentaires pour