Turn any signal into insight and action. See how PagerDuty Digital Operations Management Platform integrates machine data and human intelligence to improve visibility and agility across organizations.
Connect insights to real-time action by aligning teams through the shared language of business impact.
Check out the latest products we’ve been working on—including event intelligence, machine learning, response automation, on-call, analytics, operations health management, integrations, and more.
Digital Operations Management arms organizations with the insights needed to turn data into opportunity across every operational use case, from DevOps, ITOps, Security, Support, and beyond.
Over 300 Integrations
Discover DevOps best practices with our library of webinars, whitepapers, reports, and much more.
Learn best practices and get support help with resources from our award-winning support team.
See how PagerDuty works with our live product demo — twice a week, every week.
Join live and on-demand webinars for product deep dives, industry trends, configuration training, and use case-specific best practices.
Interactive, simple-to-use API and technical documentation enables users to easily try updates and extend PagerDuty.
Engage with users and PagerDuty experts from our global community of 200k+ users. Become a member, connect, and share insights for success.
Get all your PagerDuty-related questions answered by exploring our in-depth support documentation and community forums.
“I need to be notified if there’s a significant event ongoing with SignalFx.” This is what I tell my team. However, despite being the CTO...
PagerDuty helps organizations transform their digital operations. Learn more about PagerDuty's mission and what we do.
Meet our experienced and passionate executive team.
We are risk-taking innovators dedicated to delivering amazing products and delighting customers. Join us and do the best work of your career.
With the PagerDuty Foundation, we are committed to doing our part in giving back to the community.
LogicMonitor is a SaaS-based performance monitoring solution, enabling IT Ops teams to intelligently monitor the infrastructure, applications and services fueling their business. Using LogicMonitor’s monitoring combined with PagerDuty’s advanced on-call scheduling and alerting capabilities, you can be assured that you’ll be notified as soon as there is a problem within your infrastructure.
If you are adding your integration to an existing service, click the name of the service you want to add the integration to. Then click the Integrations tab and click the +New Integration button.
Once you have set up a PagerDuty service with the LogicMonitor integration, you can also configure PagerDuty to acknowledge LogicMonitor alerts when they are acknowledged in PagerDuty, as follows:
Once the above is complete, you should be able to acknowledge LogicMonitor alerts from PagerDuty.
By default, LogicMonitor will pre-populate four different HTTP requests, one for each of:
For each request you can select which alert statuses should trigger the HTTP request. Requests will be sent for new alerts (status: Active), and can additionally be sent for alert acknowledgements (status: Acknowledged), clears (status: Cleared) and escalations/de-escalations (status: Escalated). Note that each alert status can only be associated with one request. Since LogicMonitor auto-populates a different request for each alert status by default, you’ll have to delete a request in order to see the option to include that alert status in a different request. When editing the HTTP requests, you’ll see the following fields:
The HTTP method for PagerDuty integrations is restricted to POST
The URL that the HTTP request should be made to. This field is auto-populated based on information you’ve provided, and for this integration, should use the PagerDuty integration API endpoint (https://events.pagerduty.com/generic/2010-04-15/create_event.json).
The custom formatted alert data to be send in the HTTP POST request (used to create, update and close PagerDuty incidents). This field will be auto-populated for you. If desired, you can customize the alert data field using tokens. The following tokens are available:
datasource alert message tokens
eventsource alert message tokens
batchjob alert message tokens
Include an ID provided in HTTP response when updating alert status
Check this option if you’d like LogicMonitor to find the PagerDuty incident ID returned in the response to the HTTP request associated with a new alert, and use the ID in any subsequent requests for alert acknowledgements, clears and escalations/de-escalations. By default, this option will be selected.
HTTP Response Format
If LogicMonitor is to use the ID provided in the response, select the format the response will be in.
Once you have configured your integration and triggered an alert, you will see that an incident is triggered within PagerDuty. Once the alert clears, the incident in PagerDuty will be resolved.
With the default HTTP Requests, as soon as an alert clears in LogicMonitor it will also resolve the incident in PagerDuty. If incidents are not automatically resolving within PagerDuty, ensure alert clear messages are not suppressed in your LogicMonitor implementation.
Once you have a second LogicMonitor service set up within PagerDuty, create a new external alert within LogicMonitor. You will duplicate the “In LogicMonitor” section above, this time using the PagerDuty Service Integration Key from the additional PagerDuty service on which you’d like to trigger an incident.
If you are having trouble completing the installation, please contact our support team.
600 Townsend St., #200
San Francisco, CA 94103
905 King Street West, Suite 600
Toronto, ON, M6K 3G9, Canada
1416 NW 46th St., St. 301
Seattle, WA 98107
5 Martin Place
1 Fore St,
London EC2Y 9DT
© 2009 - 2018