Get Notified in Service Now (SNOW)

• When your Cloud resources are Parked (Shut down, Started) by Turbonomic, receive notification at your SNOW endpoints
• WorkFlow (Webhooks) could be used to configure SNOW endpoint URLs for the Turbonomic Parking actions

Why we need this?

• To be informed on your resource status when there are disruptive actions taken external from your Cloud environment
• Helps to prepare the application based on the informed status of actions

Parking Actions

• IBM Turbonomic Parking action is not a Market action, whereas they are generated out of the user defined mode of execution
  
• Parking actions enforces the Workload entities to powered off state in their Public cloud platforms, when they are not intended to be used, during maintenance windows…. 
  
• Parking Actions “Stop” and “Start” could be executed on the Cloud resource or Workload entity that is Eligible/Parkable, from Turbonomic UI & APIs 

Mode of Parking actions:

Eligible/Parkable Workloads: For Webhooks (As on 8.15.2)

Parking actions: Goal

Parking Actions: Notifications

 

Notifications: UI

• Parking action execution status, resulting in the “All Actions” widget along with other Market actions
• Stop & Start actions on the Parkable workloads could be seen from the widget and the data could be extracted for reporting

 

Cloud > Add Widget > Actions (Tabular – Chart type)

 

 

Notifications: Webhooks 

• Various Webhooks (Workflow) End Points that are supported (REST API Compatible) in Turbonomic (Slack, ServiceNow, Web Services, IBM CP4WatsonAIOps…)
• Parking actions (For Virtual Machines) as on 8.15.0 are supported 

Webhooks

 

• Webhooks are automated messages based on the Action state, result (say) could be sent to the external applications, platforms that supports Rest API 
• Webhooks endpoint applications to be configured in Turbonomic > Settings > Workflows

 

Service Now: Webhooks End Point

 

Pre-requisite

• Service Now end point that complies to the Rest APIs standards to be configured in the Workflows

How to automate the Webhooks (Workflow)?

 

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:

1. Configure a new Workflow (Settings > Workflow)
2. (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:

--- IBM Turbonomic Documentation

https://www.ibm.com/docs/en/SSFV9Z_8.x.0/ux-app/_tasks/webhooks_Create_Workflow_Editor.html 

 

How to Test/Validate?

Service Now: Webhook Validation

Validate SNOW Change Request for Every Parking action executed:

 

1. After the successful Parking action execution (Start/Stop), login to SNOW Console and verify the ticket Created (here in this case, a Change Request
2. Verify the Change request created in the SNOW console, where the message description is displayed based on the content provided in the Request body
3. Service now - Business rules could be configured to manage the CR workflow (e.g., auto close after creation)

--- For more feedback/Add Ideas

https://ideas.ibm.com