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

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

Oracle Enterprise Manager Integration

Oracle Enterprise Manager is a set of systems management tools provided by Oracle Corporation for managing the Oracle environment. It provides tools to monitor the Oracle environment and automate tasks to make database and application administration easier.

OpsGenie is an alert and notification management solution that is highly complementary to Oracle Enterprise Manager.

What does OpsGenie offer to OEM users?

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

Functionality of the integration

  • When an incident is created in Oracle Enterprise Manager, an alert is created in OpsGenie automatically through the integration.

Add Oracle Enterprise Manager Integration in OpsGenie

  1. Please create an OpsGenie account if you haven't done already
  2. Go to OpsGenie Oracle Enterprise Manager Integration page,
  3. Specify who should be notified for Oracle Enterprise Manager alerts using the "Teams" field. Auto-complete suggestions will be provided as you type.
  4. Click on "Save Integration".

OpsGenie Oracle Enterprise Manager Plugin

For Red Hat Based Distributions

  1. Download OpsGenie Oracle Enterprise Manager plugin.
  2. Run following command:
sudo rpm -i opsgenie-oem-<your_version>.rpm

For Debian Based Distributions

  1. Download OpsGenie Oracle Enterprise Manager plugin.
  2. Run following command:
sudo dpkg -i opsgenie-oem-<your_version>.deb

Steps After Downloading the Plugin

  1. After installation, the configuration file for the plugin (opsgenie-integration.conf) will be located in "/etc/opsgenie/conf".
  2. Edit this file and put your API Key for OEM integration in "apiKey" key replacing "<your_opsgenie_integrarion_api_key>".
  3. Save the configuration file.
Configuration Parameters

apiKey

Copy the API key from the Oracle Enterprise Manager integration you've created above. oem2opsgenie 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

Teams field is used to specify which teams should be notified for the Oracle Enterprise Manager 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 Oracle Enterprise Manager integration, Advanced Settings page.

tags

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

logPath

Specifies the full path of the log file. (Default value is /var/log/opsgenie/oem2opsgenie.log)

oem2opsgenie.http.proxy.enabled

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

oem2opsgenie.http.proxy.host

It is the port of the proxy.

oem2opsgenie.http.proxy.port

It is the port of the proxy.

oem2opsgenie.http.proxy.scheme

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

oem2opsgenie.http.proxy.username

It is the Proxy authentication username.

oem2opsgenie.http.proxy.password

It is the Proxy authentication password.

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 Dynamic Fields document.

You can configure the golang-executable to use a proxy for sending HTTP requests by defining the environment variable HTTP_PROXY=http://host:port

Configuration in Oracle Enterprise Manager

  1. In Oracle Enterprise Manager, click on "Setup" drop-down menu on the top-right.
  2. Hover on "Notifications" tab, click on "Scripts and SNMPv1 Traps" from the menu.
  3. Select "OS Command" from the drop-down menu on the right and click on "Go" button.
  4. Give the command a name in "Name" field. (e.g. oem2opsgenie)
  5. You can give this command a description in "Description" field but, it's optional.
  6. Copy
/etc/opsgenie/oem2opsgenie

and paste it into "OS Command" field.

  1. You can give apiKey, teams and tags parameters to this command. (e.g. /etc/opsgenie/oem2opsgenie -apiKey c193179e-4e72-43f4-b211-cdd0b029132f -teams "team1,team2" -tags "tag1,tag2")
    Or you can give this parameters in the configuration file.
  2. If you use command-line parameters, it'll override the same parameter from configuration file.
  3. Teams and tags parameters are optional but, you have to configure the API key of the integration either as a command-line argument to OEM OS Command or as a configuration in the configuration file.
  4. Click on "OK" button on the bottom-right.
  5. Now you can use this notification method in your incident rules as an action.
  6. All you have to do is selecting "oem2opsgenie (OS Command)" in "Advanced Notifications" tab when adding a new action to the rule.

Sample Webhook Message from OpsGenie OEM Plugin

{
            "ASSOC_EVENT_COUNT": "1",
            "CATEGORIES_COUNT": "1",
            "CATEGORY_1": "Capacity",
            "CATEGORY_CODES_COUNT": "1",
            "CATEGORY_CODE_1": "Capacity",
            "ESCALATED": "No",
            "ESCALATED_LEVEL": "0",
            "EVENT_SOURCE_1_HOST_NAME": "WIN-NAMD8F7JLL1",
            "EVENT_SOURCE_1_TARGET_GUID": "A0D26BACFF431D97FF36B90D82811004",
            "EVENT_SOURCE_1_TARGET_NAME": "WIN-NAMD8F7JLL1",
            "EVENT_SOURCE_1_TARGET_OWNER": "SYSMAN",
            "EVENT_SOURCE_1_TARGET_TYPE": "host",
            "EVENT_SOURCE_1_TARGET_URL": "https://WIN-NAMD8F7JLL1:7799/em/redirect?pageType",
            "EVENT_SOURCE_1_TARGET_VERSION": "6.3.9600.0.0",
            "EVENT_SOURCE_2_HOST_NAME": "WIN-NAMD8F7JLL2",
            "EVENT_SOURCE_2_TARGET_GUID": "A0D26BACFF431D97FF36B90D82811005",
            "EVENT_SOURCE_2_TARGET_NAME": "WIN-NAMD8F7JLL2",
            "EVENT_SOURCE_2_TARGET_OWNER": "SYSMAN2",
            "EVENT_SOURCE_2_TARGET_TYPE": "host2",
            "EVENT_SOURCE_2_TARGET_URL": "https://WIN-NAMD8F7JLL1:7799/em/redirect?pageType2",
            "EVENT_SOURCE_2_TARGET_VERSION": "6.3.9600.0.2",
            "EVENT_SOURCE_COUNT": "2",
            "INCIDENT_ACKNOWLEDGED_BY_OWNER": "No",
            "INCIDENT_CREATION_TIME": "Oct 10, 2016 7:26:50 AM GMT",
            "INCIDENT_ID": "30",
            "INCIDENT_STATUS": "New",
            "ISSUE_TYPE": "2",
            "LAST_UPDATED_TIME": "Oct 10, 2016 7:26:50 AM GMT",
            "MESSAGE": "CPU Utilization is 12.746%, crossed warning (2) or critical (10) threshold.",
            "MESSAGE_URL": "https://WIN-NAMD8F7JLL1:7799/em/redirect?pageType",
            "NOTIF_TYPE": "NOTIF_NORMAL",
            "ORCL_GTP_OS": "Windows",
            "ORCL_GTP_PLATFORM": "x64 (AMD or Intel)",
            "PRIORITY": "None",
            "PRIORITY_CODE": "PRIORITY_NONE",
            "REPEAT_COUNT": "0",
            "RULESET_NAME": "Prod Rule Set",
            "RULE_NAME": "Prod Rule Set,rule 132",
            "RULE_OWNER": "SYSMAN",
            "SEVERITY": "Critical",
            "SEVERITY_CODE": "CRITICAL",
            "SEVERITY_SHORT": "CR",
            "SystemRoot": "C:\\Windows",
            "UPDATES": "Incident created by rule (Name ",
            "UPDATES_1": "Incident created by rule (Name ",
            "UPDATES_COUNT": "1",
            "USER_DEFINED_TARGET_PROP": "Operating System",
            "apiKey": "1234-abcd-5678-efgh",
            "tags": "tag1,tag2",
            "teams": "team1,team2"
}

Sample alert

Oracle Enterprise Manager Integration