troubleshooters
Creates, updates, deletes, gets or lists a troubleshooters
resource.
Overview
Name | troubleshooters |
Type | Resource |
Id | azure_extras.help.troubleshooters |
Fields
The following fields are returned by SELECT
queries:
- get
Successful fetched Troubleshooter instance.
Name | Datatype | Description |
---|---|---|
properties | object | Troubleshooter Instance properties. |
Methods
The following methods are available for this resource:
Name | Accessible by | Required Params | Optional Params | Description |
---|---|---|---|---|
get | select | scope , troubleshooterName | Gets troubleshooter instance result which includes the step status/result of the troubleshooter resource name that is being executed. Get API is used to retrieve the result of a Troubleshooter instance, which includes the status and result of each step in the Troubleshooter workflow. This API requires the Troubleshooter resource name that was created using the Create API. | |
create | insert | scope , troubleshooterName | Creates the specific troubleshooter action under a resource or subscription using the ‘solutionId’ and ‘properties.parameters’ as the trigger. Azure Troubleshooters help with hard to classify issues, reducing the gap between customer observed problems and solutions by guiding the user effortlessly through the troubleshooting process. Each Troubleshooter flow represents a problem area within Azure and has a complex tree-like structure that addresses many root causes. These flows are prepared with the help of Subject Matter experts and customer support engineers by carefully considering previous support requests raised by customers. Troubleshooters terminate at a well curated solution based off of resource backend signals and customer manual selections. | |
continue | exec | scope , troubleshooterName | Uses ‘stepId’ and ‘responses’ as the trigger to continue the troubleshooting steps for the respective troubleshooter resource name. Continue API is used to provide inputs that are required for the specific troubleshooter to progress into the next step in the process. This API is used after the Troubleshooter has been created using the Create API. | |
end | exec | scope , troubleshooterName | Ends the troubleshooter action | |
restart | exec | scope , troubleshooterName | Restarts the troubleshooter API using applicable troubleshooter resource name as the input. It returns new resource name which should be used in subsequent request. The old resource name is obsolete after this API is invoked. |
Parameters
Parameters can be passed in the WHERE
clause of a query. Check the Methods section to see which parameters are required or optional for each operation.
Name | Datatype | Description |
---|---|---|
scope | string | The scope at which the operation is performed. |
troubleshooterName | string | Troubleshooter resource Name. |
SELECT
examples
- get
Gets troubleshooter instance result which includes the step status/result of the troubleshooter resource name that is being executed.
Get API is used to retrieve the result of a Troubleshooter instance, which includes the status and result of each step in the Troubleshooter workflow. This API requires the Troubleshooter resource name that was created using the Create API.
SELECT
properties
FROM azure_extras.help.troubleshooters
WHERE scope = '{{ scope }}' -- required
AND troubleshooterName = '{{ troubleshooterName }}' -- required
;
INSERT
examples
- create
- Manifest
Creates the specific troubleshooter action under a resource or subscription using the ‘solutionId’ and ‘properties.parameters’ as the trigger.
Azure Troubleshooters help with hard to classify issues, reducing the gap between customer observed problems and solutions by guiding the user effortlessly through the troubleshooting process. Each Troubleshooter flow represents a problem area within Azure and has a complex tree-like structure that addresses many root causes. These flows are prepared with the help of Subject Matter experts and customer support engineers by carefully considering previous support requests raised by customers. Troubleshooters terminate at a well curated solution based off of resource backend signals and customer manual selections.
INSERT INTO azure_extras.help.troubleshooters (
data__properties,
scope,
troubleshooterName
)
SELECT
'{{ properties }}',
'{{ scope }}',
'{{ troubleshooterName }}'
RETURNING
properties
;
# Description fields are for documentation purposes
- name: troubleshooters
props:
- name: scope
value: string
description: Required parameter for the troubleshooters resource.
- name: troubleshooterName
value: string
description: Required parameter for the troubleshooters resource.
- name: properties
value: object
description: |
Troubleshooter Instance properties.
Lifecycle Methods
- continue
- end
- restart
Uses ‘stepId’ and ‘responses’ as the trigger to continue the troubleshooting steps for the respective troubleshooter resource name.
Continue API is used to provide inputs that are required for the specific troubleshooter to progress into the next step in the process. This API is used after the Troubleshooter has been created using the Create API.
EXEC azure_extras.help.troubleshooters.continue
@scope='{{ scope }}' --required,
@troubleshooterName='{{ troubleshooterName }}' --required
@@json=
'{
"stepId": "{{ stepId }}",
"responses": "{{ responses }}"
}'
;
Ends the troubleshooter action
EXEC azure_extras.help.troubleshooters.end
@scope='{{ scope }}' --required,
@troubleshooterName='{{ troubleshooterName }}' --required
;
Restarts the troubleshooter API using applicable troubleshooter resource name as the input.
It returns new resource name which should be used in subsequent request. The old resource name is obsolete after this API is invoked.
EXEC azure_extras.help.troubleshooters.restart
@scope='{{ scope }}' --required,
@troubleshooterName='{{ troubleshooterName }}' --required
;