Actions

Introduction

Actions are an integral part of the monitoring ecosystem, where problems and issues are addressed and resolved. Actions can vary widely and come with several considerations:

Manual vs. Automated Actions: Determining whether the action should be manually executed by an operator or automatically by the system.
Approvals Required: Identify necessary approvals before executing the action.
Type of Action: Specifying the nature of the action, such as restarting a service, scaling resources, or sending notifications.
Nature of the Impact: Understanding the potential impact of the action on the system and its users.

The Virtana Wisdom supports the full lifecycle management of action configurations, including Create, Read, Update, and Delete (CRUD) operations. Each operation includes specific steps that interact with user interface elements.

Create an Action Configuration

Navigate to Settings > Actions Configuration.
Click on the "Add Action" button. Select the action type from the drop-down menu.
You can select actions such as Slack, MatterMost, Teams, Https, and WebEx
Enter the "Name" in the Name input field.
Enter the "Webhook URL" in the Webhook URL input field.
To test if the webhook URL is correct, click on Send Message.
Click Add Action to save.

Update Action Configuration

Locate an existing action configuration in the list.
Click the "Action Name" in the row go to the edit configuration.
Update the necessary fields (e.g., Name, Webhook URL).
Click the "Save" button.

Delete Action Configuration

Locate an existing action configuration in the list.
Click the "Delete" icon next to the configuration.
In the confirmation dialog, click "OK".

List Action Configurations

Navigate to Configurations List:
- Click on Settings > Actions menu item
A list of all available action configurations is displayed.

Search Action Configuration by Name

Click on Settings > Actions menu.
Locate the search bar or search input field at the top of the configurations list page.
Enter the name (or part of the name) of the action configuration you want to search for.
Click the "Search" button.
The list of action configurations remains filtered based on the search query until the search input is cleared or a new search is performed.

Default Action Policy

For each category of alarms (Info, Warning, and Critical), select the appropriate actions to be triggered. These actions can include notifications, alerts, or any predefined responses based on the severity of the alarm. Action configuration supports setting multiple actions, allowing you to configure various action types for both rules and actions settings.

Alarm Rules

To create Alarm rule:

Navigate to Alarms >Rules >Create New Rule.
To set up a new rule, choose the option for multiple action types as the target for notifications
Based on the selections made in the rule configuration screen, the chosen multiple action types will be triggered, and notifications will be sent using the action service.
For existing rules, you can edit and modify the action type selections as needed.

Create an HTTP Configuration

Here are the steps to use the newly added HTTP action type

Navigate to Settings > Administration >Action menu.
To create a new action, select Add Action from the drop-down menu and choose the HTTP type.
Provide the Name, HTTP endpoint URL, JSON data payload. (Refer to the sample)
Add the HTTP header key value pair. (Refer to the sample)

Note

Following is the sample JSON and the Header key values to enter.

In a document, we must provide a json sample format as an input. Refer to the following sample json for more details:

{  
	"title": "${title}", 
	"titleLink": "${link}", 
	"ruleId": "${ruleId}",  
	"caseId": "${caseId}",  
	"caseName": "${caseName}",  
	"caseDescription": "${caseDescription}",  
	"openTime": "${openTime}", 
	"entityName": "${entityName}",  
	"entityType": "${entityType}",  
	"ruleName": "${ruleName}", 
	"ruleType": "${ruleType}",  
	"thresholdValues":
	 [  
		<#list thresholdValues as value>   
	 {     
		"gaugeName": "${value.gaugeName}", 
	        "threshold": ${value.threshold?c},     
		"exceededValue": ${value.exceededValue?c}  
	 }	
		<#if value_has_next>, </#if>
 	  	</#list>
	 ], 
	 "sourceUuid": "${sourceUuid}",
	 "severity": "${severity}"

	 }

Description

${title}: Case name
${link}: Applaince Case Url
${ruleId}: Case Rule Id,
${caseId}: Case Id
${caseName}: Case name
${caseDescription}: Case Description
${openTime}: Case Open Time (e.g., 2024-10-25 03:05:00 PDT)
${entityName}: Entity Name (e.g., qe-appdisc-01.lab.vi.local)
${entityType}: Entity Type (e.g., ESXHost)
${ruleName}: Alarm Rule Name
${ruleType}: Alarm Rule Type
${sourceUuid}: Applaince UUID
${severity}: Case severity (e.g.,info, warning, critical)Threshold Values List (#list thresholdValues as value)
${value.gaugeName}: Gauge Name
${value.threshold}: Threshold
${value.exceededValue}: Exceeded Value

Header key values to enter:

{ "Accept": "application/json"}

Here is the snippet

ServiceNow event notification via Actions

The ServiceNow event notification can be received via Actions in the Virtana environment. To integrate this, use the following sample JSON data playload:

{
    "records": [
        {
            "source": "Virtana",
            "event_class": "${sourceUuid}",
            "resource": "${entityName}",
            "node": "${sourceUuid}",
            "metric_name": "${caseName}",
            "type": "${entityType}",
            "severity": "1",
            "description": "${caseDescription}",
            "additional_info": "${link}"
        }
    ]
}

Enter the following in the Header key value pair section:

{
"Content-Type": "application/json",
"Authorization": "Basic xxxxx"
}

The above JSON will help you generate the token. Use the following command to push/trigger the notification.

echo $(echo -n 'username@password' | base64)

In this section:

Actions

Note

Search results