Outgoing Webhook

OverOps allows you to fully customize alerts using raw event and threshold data flowing into the selected HTTP endpoint.

1. Open Settings by clicking Settings in the top right corner of the OverOps dashboard.

This opens the Settings dashboard for the environment you're in (you can see the environment in the upper left corner of the screen).

2. Go to General Settings > Alerts.
3. Click the Webhook tab.

4. To receive the outgoing Webhook traffic, implement an HTTP endpoint in a web-facing server.
5. From the Webhook tab, enter the URL to receive the outgoing Webhook traffic.

📘

Only admin users (account owners and admins) are authorized to change default integration settings.

Examples of Webhooks can be found here.

Once the Webhook endpoint is configured, OverOps sends a JSON message to that endpoint whenever an alert you configured gets triggered.

The tables below, describe the different message structures:
JSON structure
All alerts have the following skeleton:

{
    api_version: "0.1",
    type: "...",
    date: ...,
    username: "...",
    service_id: "...",
    service_name: "...",
    data: {
        type: "NEW_EVENT",
        summary: "...",
        view_name: "...",
        added_by: ["..."],
        data: {
            ...
        }
    }
}

The 'data' object represents the alert payload, and consists of the following:

New event payload structure:

{
    type: "...",
    location: {
        ...
    },
    entry_point: {
        ...
    },
    stacktrace: [{
        ...
    }, {
        ...
    },
    ...],
    link: "...",
    server_name: "...",
    app_name: "..."
}

For events of type "EXCEPTION", the following fields will also be present:

For events of type "LOG", the following fields will also be present:

For events of type "HTTP_ERROR", the following fields will also be present:

Locations, entry points and stack traces are made up of frames, each with the following structure:

{
    class_name: "...",
    method_name: "...",
    method_desc: "...",
    full_name: "...",
    is_3rd_party: true/false,
    is_catch_frame: true/false,
    is_hit_frame: true/false,
    modification_timestamp: ...
}

Threshold alert payload structure:

{
    threshold: ...,
    times: ...,
    from_timestamp: ...,
    to_timestamp: ...,
    top_events: [{
        ...
    }, {
        ...
    }]
}

Top event objects have the following structure:

{
    title: "...",
    frame: {
        ...
    },
    times: ...,
    link: "..."
}

Open Source Example WebHooks

❗️

The Webhooks below listed are not supported and are provided as is!

OverOps WebHook Example
Rational Team Concert JAZZ CCM Webhook
VictorOps Webhook
Rally (CA-Agile Central) Webhook
Pivotal Tracker Webhook