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

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

Scout Integration

Scout is agent based, extensible server and application monitoring service. OpsGenie is an alert and notification management solution that is highly complementary to Scout.

Scout plugin system allows developers to create plugins to extend its functionality, monitor any application and system resource, and trigger alerts to notify relevant people when necessary. Scout can not only alert for typical server problems, simple thresholds, etc. but also can do sophisticated trending, detect relative changes etc.

What does OpsGenie offer to Scout users?

Stay connected when you're mobile

Using OpsGenie, Scout users can receive notifications for critical alerts via SMS, phone calls, and iOS & Android push notifications, and can respond to the alerts directly from their mobile devices using OpsGenie apps.

Consolidated alert & notification management

Scout users can leverage OpsGenie to aggregate and manage alerts not only from Scout but also from other sources. OpsGenie enables users to maintain their own notifications information and preferences, eliminating the burden to keep this information current and accurate in multiple disparate tools.

Alert life cycle management

For Scout users, OpsGenie integration provides full alert life cycle management capabilities. Using OpsGenie, users can not only receive notifications for critical problems detected by Scout, but also acknowledge alerts, take or assign ownership of the alerts, comment on them, etc. rapidly no matter when and where they may receive the alerts. OpsGenie keeps track of all alert activity seamlessly: when the alert was created, who was notified when and how, whether and when recipients have seen the alert, acknowledged it, who executed which action, etc. OpsGenie can also automatically close alerts when host/service comes back up.

Alerts that empower

A short text message (SMS) typically used to notify users often fails to convey sufficient information to enable the recipients to assess the problem and determine the right course of action. OpsGenie alerts are not limited to couple hundred characters of text, includes many fields, tags, and attached files . Recipients can not only see the alert message but all the supporting information, charts, etc. and figure out what to do next. You can attach any information that you think as relevant to the alert and make it available to the recipients, either via the API or the web UI.

Functionality of the integration

  • When an alert is created in Scout, an alert is created in OpsGenie.
  • When an alert is closed in the Scout, the alert is closed in OpsGenie.

Add Scout integration to OpsGenie

OpsGenie Scout integration provides sensible defaults. Basic configuration settings contain the minimum configuration information required to make the integration work.

  1. Please create an OpsGenie account if you haven't done already
  2. Go to OpsGenie Scout Integration page,
  3. Specify who should be notified for the Scout alerts using the "Recipients" field. User(s), group(s), escalations policies and on-call schedules can be specified as the alert recipients. Auto-complete suggestions will be provided as you type.
  4. Click on "Save Integration"
  5. Copy the integration URL by clicking on the copy button or selecting. URL includes OpsGenie endpoint as well as the API key.

Configuring a webhook in Scout

  1. Go to "Notifications" page
  1. In "Notification Channels", click on "Add Webhook"
  1. Paste the integration URL from OpsGenie into the "Webhook URL" field, and click on Submit.
  1. Go back to the "Notifications" page, and add OpsGenie Webhook to the relevant Notification Groups.

Advanced Configuration Settings Expand

OpsGenie Scout integration uses sensible configuration defaults to make the integration as easy as possible. However, it is also possible to customize the integration. Advanced settings allow:

  • Defining different rules to notify different people for different alerts
  • Modifying alert content using Scout webhook payload

The following variables from Scout alert webhook payload are available when defining filters and when setting the alert fields values:

  • Lifecycle
  • Severity
  • Metric Name
  • Metric Value
  • Plugin Name
  • Server Host Name
  • Server Name
  • Time
  • Title
  • Url
  • Metric Chart Url

You can create multiple rules with filters using the variables from Scout webhook payload. For each rule, alert fields can have different values, hence different people can be notified, alerts can have different tags, etc.

Sample payload sent from Scout Close

{
  "event_name": "new_item",
  "data": {
    "item": {
      "public_item_id": null,
      "integrations_data": {},
      "last_activated_timestamp": 1390917586,
      "hash": "1cbf07b5da947216f68ea8b8dd4813fa43317b90",
      "id": 274146948,
      "environment": "staging",
      "title": "ReferenceError: Uncaught ReferenceError: testing_rollbar_123 is not defined",
      "last_occurrence_id": 770525810,
      "last_occurrence_timestamp": 1390917588,
      "platform": 1,
      "first_occurrence_timestamp": 1390917586,
      "project_id": 6869,
      "resolved_in_version": 6,
      "status": 1,
      "unique_occurrences": null,
      "framework": 7,
      "total_occurrences": 1,
      "level": 40,
      "counter": 1,
      "first_occurrence_id": 770525810,
      "activating_occurrence_id": 770525810
    }
  }
}

Sample alert

Scout Integration