Docs
WebsiteLoginFree Trial
  • Getting Started
    • OnCall Users
    • Team Admins
    • Account Admins
  • Architecture Guide
  • Common UI Design Patterns
  • Alerts
  • Teams
  • Schedules
  • Escalation Policies
  • Integrations
  • Broadcasts
  • Users
  • Notifications
  • Reports
  • Billing
  • Accounts
  • Stakeholders
  • Maintenance Windows
  • Routers
  • Notification Rules
  • Single Sign On (SSO)
  • Integration Guides
    • Introduction
    • 66uptime
    • Apex Ping
    • AppDynamics
    • Auvik
    • AWS CloudWatch
    • Azure Monitor
    • Cloudflare
    • Cronitor
    • Datadog
    • Dead Man's Snitch
    • Echoes HQ
    • ElastAlert
    • Email
    • Form
    • Freshdesk
    • Freshservice
    • Google Hangouts Chat
    • Grafana
    • Healthchecks.io
    • HetrixTools
    • Honeybadger
    • Hydrozen
    • Jira Server
    • JotForm
    • Kapacitor
    • LogicMonitor
    • Mattermost
      • Outgoing Webhook
      • Post to Channel
    • Meta Workplace
    • Microsoft Teams
    • New Relic
    • Outgoing Webhook
    • Pingdom
    • Prometheus
    • PRTG Network Monitor
    • Pulsetic
    • Sentry
    • ServerGuard24
    • Site24x7
    • Slack
      • Notifications
      • Outgoing Webhook
      • Post to Channel
    • SolarWinds
    • Stackdriver
    • StatusCake
    • Twilio
      • Incoming SMS
      • Live Call Routing
    • Typeform
    • Uptime
    • Uptime Kuma
    • UptimeRobot
    • Webhook
    • Zendesk
  • API
    • Introduction
    • Authentication
    • Errors
    • Pagination and Filters
    • Common Model Attributes
    • Account Users
    • Alerts
    • Broadcasts
    • Comments
    • Escalation Policies
    • Events
    • Integrations
    • Logs
    • Maintenance Windows
    • Notification Rules
    • Routers
    • Schedules
    • Teams
    • Users
  • Command Line Interface (CLI)
    • PagerTree CLI: Command Line Interface
Powered by GitBook
On this page
  • What is Echoes HQ?
  • How It Works
  • Integration Walkthrough
  • In Echoes HQ
  • In PagerTree

Was this helpful?

  1. Integration Guides

Echoes HQ

Send your PagerTree alerts to Echoes HQ.

PreviousDead Man's SnitchNextElastAlert

Last updated 3 months ago

Was this helpful?

Company
Estimated Time
Vendor Docs
Open Source

1 minute

What is Echoes HQ?

gives comprehensive insights into your teams to understand how they are progressing and spot bottlenecks and areas of improvement.

How It Works

PagerTree sends your PagerTree alerts to Echoes HQ when:

  • alert.created- When an alert is created in PagerTree, PagerTree will create an incident in Echoes HQ.

  • alert.acknowledged- When an alert is acknowledged in PagerTree, PagerTree will update the incident in Echoes HQ.

  • alert.resolved- When an alert is resolved in PagerTree, PagerTree will update the incident in Echoes HQ.

Integration Walkthrough

This integration tutorial will show you how to connect PagerTree to Echoes HQ. The estimated time for this integration is 1 minute. We assume that you already have a PagerTree and Echoes HQ account setup.

In Echoes HQ

  1. in Echoes HQ.

In PagerTree

  1. Paste your newly created Echoes HQ API Key into PagerTree.

  2. Click Create.


You have successfully completed the Echoes HQ Integration.


by clicking the Echoes HQ logo.

Echoes HQ
Create an API Key
Echoes HQ Inc.
view
v3.rb
Create the integration