Diagnostics interface
Interface representing a Diagnostics.
Methods
| begin |
Diagnostics tells you precisely the root cause of the issue and how to address it. You can get
diagnostics once you discover and identify the relevant solution for your Azure issue. |
| begin |
Diagnostics tells you precisely the root cause of the issue and how to address it. You can get
diagnostics once you discover and identify the relevant solution for your Azure issue. |
| check |
This API is used to check the uniqueness of a resource name used for a diagnostic check. |
| get(string, string, Diagnostics |
Get the diagnostics using the 'diagnosticsResourceName' you chose while creating the diagnostic. |
Method Details
beginCreate(string, string, DiagnosticsCreateOptionalParams)
Diagnostics tells you precisely the root cause of the issue and how to address it. You can get
diagnostics once you discover and identify the relevant solution for your Azure issue.
You
can create diagnostics using the ‘solutionId’ from Solution Discovery API response and
‘additionalParameters’
Note: ‘requiredParameterSets’ from Solutions Discovery API
response must be passed via ‘additionalParameters’ as an input to Diagnostics API
function beginCreate(scope: string, diagnosticsResourceName: string, options?: DiagnosticsCreateOptionalParams): Promise<SimplePollerLike<OperationState<DiagnosticResource>, DiagnosticResource>>Parameters
- scope
-
string
This is an extension resource provider and only resource level extension is supported at the moment.
- diagnosticsResourceName
-
string
Unique resource name for insight resources
- options
- DiagnosticsCreateOptionalParams
The options parameters.
Returns
Promise<@azure/core-lro.SimplePollerLike<OperationState<DiagnosticResource>, DiagnosticResource>>
beginCreateAndWait(string, string, DiagnosticsCreateOptionalParams)
Diagnostics tells you precisely the root cause of the issue and how to address it. You can get
diagnostics once you discover and identify the relevant solution for your Azure issue.
You
can create diagnostics using the ‘solutionId’ from Solution Discovery API response and
‘additionalParameters’
Note: ‘requiredParameterSets’ from Solutions Discovery API
response must be passed via ‘additionalParameters’ as an input to Diagnostics API
function beginCreateAndWait(scope: string, diagnosticsResourceName: string, options?: DiagnosticsCreateOptionalParams): Promise<DiagnosticResource>Parameters
- scope
-
string
This is an extension resource provider and only resource level extension is supported at the moment.
- diagnosticsResourceName
-
string
Unique resource name for insight resources
- options
- DiagnosticsCreateOptionalParams
The options parameters.
Returns
Promise<DiagnosticResource>
checkNameAvailability(string, DiagnosticsCheckNameAvailabilityOptionalParams)
This API is used to check the uniqueness of a resource name used for a diagnostic check.
function checkNameAvailability(scope: string, options?: DiagnosticsCheckNameAvailabilityOptionalParams): Promise<CheckNameAvailabilityResponse>Parameters
- scope
-
string
This is an extension resource provider and only resource level extension is supported at the moment.
The options parameters.
Returns
Promise<CheckNameAvailabilityResponse>
get(string, string, DiagnosticsGetOptionalParams)
Get the diagnostics using the 'diagnosticsResourceName' you chose while creating the diagnostic.
function get(scope: string, diagnosticsResourceName: string, options?: DiagnosticsGetOptionalParams): Promise<DiagnosticResource>Parameters
- scope
-
string
This is an extension resource provider and only resource level extension is supported at the moment.
- diagnosticsResourceName
-
string
Unique resource name for insight resources
- options
- DiagnosticsGetOptionalParams
The options parameters.
Returns
Promise<DiagnosticResource>