Rely.io
  • 📌What is Rely.io?
  • 💡How Rely.io works
  • 📑Getting Started Guide
    • Create an account for your organization
    • Add your first plugin
    • Import services into the Service Catalog
    • Make the Software Catalog your own
    • What's Next?
  • 🌈Basic Concepts
    • Entities
    • Blueprints
    • Property Data Types
    • Catalogs
    • Data Model
    • Plugins
    • User Blueprints vs Plugin Blueprints
    • Actions and Automations
      • Automation Rules
      • Self-Service Actions
    • Home Pages
    • Scorecards
  • 📚Guides & Tutorials
    • Enhancing Deployment Visibility through Gitlab Pipelines and Rely's API
  • 🖥️Software Catalog
    • Overview and Use Cases
    • Usage Guide
      • Creating a new Entity
      • Updating an Entity
      • Tracking Entity Changes
      • Customizing an Entity's Page
      • Customizing a Catalog
      • Creating a new Blueprint & Catalog
      • Updating a Blueprint
      • Tracking Blueprint Changes
    • Relevant Guides
    • Troubleshooting
  • 🥇Scorecards
    • Overview and Use Cases
    • Usage Guide
      • Creating a Scorecard
      • Updating a Scorecard
      • Evaluating Performance
    • Scorecard Examples
      • Production Readiness Scorecard Example
      • DORA Metrics Scorecard Example
      • Operational Maturity Example
  • 🎨Home Pages
    • Overview and Use Cases
    • Usage Guide
      • Creating a New Tab
  • ⚡Self-Service Actions
    • Overview and Use Cases
    • Usage Guide
      • Configuring your Self Service Agent
      • Managing your Actions Catalog
      • Self-Service Actions as Code
      • Running Actions
      • Tracking Action Runs
  • ↗️Plugins & Automation
    • What happens when you install a Plugin?
    • Self-Hosting Plugins using Galaxy
    • 🤖Automation Rules
      • Overview and Use Cases
      • Usage Guide
        • Creating an Automation Rule
        • Updating an Automation Rule
        • Tracking Automation Changes
        • Managing Automation Suggestion
    • 🔌Plugin Installation Guides
      • ⭐AWS
      • Bitbucket
      • ⭐Flux
      • GitHub
      • GitLab
      • ⭐Google Cloud Platform (GCP)
      • ⭐Kubernetes
      • ⭐OpsGenie
      • ⭐PagerDuty
      • ⭐Snyk
      • ⭐SonarQube
  • 🌐Public API
    • Audit Logs
    • Automations & Self-Service Actions
    • Automation Suggestions
    • Blueprints
    • Dashboards & Views
    • Entities
    • Scorecards
    • Self-Service Action Runs
    • Time Series
    • Users
    • Webhooks
  • ⚙️Invite Users
  • 🛡️Security & Compliance
    • Single Sign-On (SSO)
      • SAML with Google Workspace
      • SAML with Microsoft Entra ID
      • SAML with Okta
      • OIDC with Okta
      • OIDC with Google Workspace
  • 🏥Troubleshooting
  • ❓FAQ
Powered by GitBook
On this page
  • Installation Guide
  • Setup

Was this helpful?

  1. Plugins & Automation
  2. Plugin Installation Guides

OpsGenie

PreviousKubernetesNextPagerDuty

Last updated 7 months ago

Was this helpful?

This plugin is part of Pro and Enterprise plan only

Installation Guide

Setup

Step 1: Generate an Opsgenie API Key (official docs ).

  1. Log in to your Opsgenie account and navigate to Settings → API Key Management (if you cannot find this option in your side bar under App Settings you probably do not enough the necessary permissions to create one).

  2. Click the Add New API Key button.

  3. Enter a description for the API Key, for instance, "Rely.io Integration."

  4. Set the API key to have Read and Configuration access, as needed for the integration.

  5. Click Create Key and make sure to copy and store the generated API Key securely.

Step 2: Configure Opsgenie in Rely.io

  1. Open the Rely.io application and go to Settings → Data Sources.

  2. Click on the Add Data Source button and select Opsgenie.

  3. A form will appear asking for details to complete the integration.

    • Collector Name: Assign a name for the PagerDuty data collector.

    • App Base URL: Copy the base url of your Opsgenie account (e.g. https://sunsy.app.opsgenie.com)

    • API Key: Paste the API Key you generated in Step 1.

Click on Create to establish the integration. Your plugin should now be listed in the Active section of your Data Sources.

After you submit your form, an entity discovery run will be kickstarted that can take a few minutes. By the end of this discovery run:

  • New blueprints will be added to your data model

  • Entities will be queries from the data-source and added to your software catalog

  • These entities will be periodically updated to ensure they remain in sync with their external counter-parts

↗️
🔌
⭐
here