Search results for "{{ search.query }}"

No results found for "{{search.query}}". 
View All Results

VMware Center Integration

VMware vCenter provides a centralized platform for managing your VMware vSphere environments, so you can automate and deliver a virtual infrastructure with confidence. It provides simple deployment, proactive optimization, centralized control and visibility and management. OpsGenie is an alert and notification management solution that is highly complementary to VMware vCenter's alerting mechanism.

What does OpsGenie offer VMware vCenter users?

By using OpsGenie’s VMware vCenter Integration: you can forward VMware vCenter incidents to OpsGenie. OpsGenie can determine the right people to notify based on on-call schedules, using email, text messages (SMS), phone calls, iOS & Android push notifications, and escalating alerts until the alert is acknowledged or closed.

Functionality of the integration

When an alarm is created in VMware vCenter, it creates an alert in OpsGenie.

Add VMware vCenter Integration in OpsGenie

  1. Please create an OpsGenie account if you haven't done so already.
  2. Go to OpsGenie's VMware VCenter Integration page.
  3. Specify who should be notified for VMware vCenter alerts using the "Teams" field. Autocomplete suggestions will be provided as you type.
  4. Copy the API Key.
  5. Click on "Save Integration."

Configuration in VMware vCenter

  1. Download OpsGenie VMware vCenter zip file under C:\ directory.
  2. Unzip the file under C:\ directory.
  3. Paste this API Key into C:\opsgenie\opsgenie-integration\conf\opsgenie-integration.conf file.
  4. Run vSphere Client.
  5. In vSphere VClient click Actions.
  6. Select Alarms and then New Alarm.
  7. While configuring the alarm add an action as "Run Command" and give your vcenter2opsgenie path in Configuration part.
  1. Save the alarm.

OpsGenie Plugin Configuration in VCenter

The plugin uses a golang-executable file (included in the plugin as vcenter2opsgenie) to create alerts in OpsGenie. VCenter should be configured to execute this file on events to create alerts in OpsGenie.

Setting the apiKey is required. Other configuration parameters are set to defaults that work with most VCenter implementations but may need to be modified as well.

Configuration Parameters


Copy the API key from the VCenter integration you've created above. vcenter2opsgenie uses this key to authenticate to OpsGenie. API key is also used to identify the right integration configuration that should be used to process alerts.


Teams field is used to specify which teams should be notified for the VCemter alerts. This field is used to set the default teams field value. It can be modified to route different alerts to different teams in OpsGenie VCenter integration, Advanced Settings page.


Tags field is used to specify the tags of the alert that created in Opsgenie.


Specifies the full path of the log file. (Default value is C:\opsgenie\vcenter2opsgenie.log)


vcenter2opsgenie.http.proxy.enabled field is to enable/disable external proxy configuration. The default value is false.

It is the host of the proxy.


It is the port of the proxy.


It is the proxy connection protocol. It may be http or https depending on your proxy servers. Its default value is http.


It is the Proxy authentication username.


It is the Proxy authentication password.

There are three ways to configure golang-executable file:

  1. Configuring from conf file: You can configure from C:\opsgenie\conf\opsgenie-integration.conf file. Configuring from conf file will overwrite the configurations made in the script.
  2. Configuring by using Golang Flags: You can configure by entering flags to command of the notification you created in VCenter, which is described in "Configure Triggers in VCenter" section. Use -apiKey flag for your apiKey.

If you want to send additional custom arguments, you can add them after the flags as: customArgName1 customArgValue1 customArgName2 customArgValue2
You can parse custom arguments by adding {{_payload.customArgName}} to wherever you need on the input fields.
For more information about using raw parameters please visit the Dynamic Fields document.

  1. Configuring from script: You can configure apiKey vcenter2opsgenie.go script. If you use this option, you need to build the script again and put the new executable to /usr/bin directory. You can find information about the location of the vcenter2opsgenie.go and how to build a go script in the "Source" section.

Sample payload sent from vCenter

Create Alert Payload:

    "VMWARE_ALARM_ALARMVALUE": "Event details",
    "VMWARE_ALARM_DECLARINGSUMMARY": "([Event alarm expression: Alarm created; Status ",
    "VMWARE_ALARM_EVENTDESCRIPTION": "Reconfigured testAlarm 'testAlarm' on Datacenter.  \n \nModified:  \n \ninfo.expression.expression: ((comparisons ",
    "VMWARE_ALARM_ID": "alarm-310",
    "VMWARE_ALARM_NAME": "OpsGenieAlarm",
    "VMWARE_ALARM_TARGET_ID": "datacenter-21",
    "VMWARE_ALARM_TARGET_NAME": "Datacenter",
    "VMWARE_ALARM_TRIGGERINGSUMMARY": "Event: Alarm reconfigured (1978)\nSummary: Reconfigured alarm 'testAlarm' on Datacenter.  \n \nModified:  \n \ninfo.expression.expression: ((comparisons "


This payload is parsed by OpsGenie as:

    "alarmValue": "Event details",
    "declaringSummary": "([Event alarm expression: Alarm created; Status ",
    "eventDescription": "Reconfigured testAlarm 'testAlarm' on Datacenter.  \n \nModified:  \n \ninfo.expression.expression: ((comparisons ",
    "eventDatacemter": "Datacenter",
    "eventUsername": "VSPHERE.LOCAL\\Administrator",
    "alarmID": "alarm-310",
    "alarmName": "OpsGenieAlarm",
    "newStatus": "Green",
    "oldStatus": "Yellow",
    "targetID": "datacenter-21",
    "targetName": "Datacenter",
    "triggeringSummary": "Event: Alarm reconfigured (1978)\nSummary: Reconfigured alarm 'testAlarmæ' on Datacenter.  \n \nModified:  \n \ninfo.expression.expression: ((comparisons "


Sample Alert

VMware Center Integration