Webhooks: Default Policy
Scope: Webhooks could be integrated inside the Default Policy for Virtual Machines, which enables for all Parking actions and its modes (Manual, Policies)
Notifications: Till 8.15.2, Webhooks are supported only for Virtual Machines (Workload Type) & cannot be scoped
How to configure:
- Configure a new Workflow (Settings > Workflow)
- (Say) ServiceNow endpoint in this context
- Address: Endpoint URL of SNOW (e.g., to create Change Request – CR for every Parking action executed on VMs)
- Http method: Post; Authentication: Basic (Provide valid username and password), that has the access to create CR
- Request header: Key & Value
- Request body: Media type – Text
{
"chg_model" : "Standard",
"description" : "Describes the change request.",
"short_description" : "My change request",
"type" : "Standard"
}
- Test Webhook – To validate the configuration made (Use any valid UUID of a workload from action center)
Service Now: Webhook Flow for Parking VMs
- Verify the SNOW endpoint created successfully in the Settings > Workflows
- Go to Settings > Policies > Defaults > Virtual Machine Defaults
- Under “Automation Workflow” section > Select Parking Start, Stop > Add the SNOW workflow configured in your Turbonomic Instance (After Execution)
- Add Webhook under Critical/Non-Critical Workflow options
- Before and After execution for Parking actions are with same behavior as they are dynamic schedule actions
- It takes 10 minutes for the policy changes to be effective
Please follow the steps in the Product documentation link below to validate the Steps completed so far:
Service Now: Webhook Validation
Validate SNOW Change Request for Every Parking action executed:
- After the successful Parking action execution (Start/Stop), login to SNOW Console and verify the ticket Created (here in this case, a Change Request
- Verify the Change request created in the SNOW console, where the message description is displayed based on the content provided in the Request body
- Service now - Business rules could be configured to manage the CR workflow (e.g., auto close after creation)