Skip to main content

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: Identifying 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

Actions.png

  1. Navigate to Settings > Actions Configuration.

  2. 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

  3. Enter the "Name" in the Name input field.

  4. Enter the "Webhook URL" in the Webhook URL input field.

  5. To test if the webhook URL is correct, click on Send Message.

  6. Click Add Action to save.

    action_policy.png

Update Action Configuration

  1. Locate an existing action configuration in the list.

  2. Click the "Action Name" in row go to the edit configuration.

  3. Update the necessary fields (e.g., Name, Webhook url).

  4. Click the "Save" button.

Delete Action Configuration

  1. Locate an existing action configuration in the list.

  2. Click the "Delete" icon next to the configuration.

  3. In the confirmation dialog, click "OK".

List Action Configurations

  1. Navigate to Configurations List:

    • Click on Settings > Actions menu item

  2. A list of all available action configurations is displayed.

Search Action Configuration by Name

search_action.png

  1. Click on Settings > Actions menu.

  2. Locate the search bar or search input field at the top of the configurations list page.

  3. Enter the name (or part of the name) of the action configuration you want to search for.

  4. 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.

default_action.png

Alarm Rules

To create Alarm rule:

  1. Navigate to Alarms >Rules >Create New Rule.

  2. To set up a new rule, choose the option for multiple action types as the target for notifications

  3. 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.

  4. For existing rules, you can edit and modify the action type selections as needed.

metric_rule.png

Create an HTTP Configuration

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

  1. Navigate to Settings > Administration >Action menu.

  2. To create a new action, select Add Action from the drop-down menu and choose the HTTP type.

  3. Provide the Name, HTTP endpoint URL, JSON data payload (below is the sample), and HTTP header (optional).

In document we have to provide json sample formate as input, here is document for more detail:

{
  "Title": "${title}",
  "Title Link": "${link}",
  "Rule Id": "${ruleId}",
  "Case Id": "${caseId}",
  "Case Name": "${caseName}",
  "Case Description": "${caseDescription}",
  "Open Time": "${openTime}",
  "Entity Name": "${entityName}",
  "Entity Type": "${entityType}",
  "Rule Name": "${ruleName}",
  "Rule Type": "${ruleType}",
  "Threshold Values": [
    <#list thresholdValues as value>
    {
      "Gauge Name": "${value.gaugeName}",
      "Threshold": "${value.threshold}",
      "Exceeded Value": "${value.exceededValue}"
    }<#if value_has_next>,</#if>
    </#list>
  ],
  "Source Uuid": "${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

action.png
In this section: