Cmd + PagerDuty

Simplified Incident Response

Speed up incident response and resolution on Production Linux with high-fidelity telemetry and full context at your fingertips.

# Protecting Linux Production Environments with PagerDuty

PagerDuty allows businesses to receive an alert anytime something anomalous—i.e. out of the ordinary or concerning—takes place within systems. With a wide range of native integrations and an API that can be used to extend functionality to just about any tool or environment, all backed by rich customizations, PagerDuty can be used to protect almost any application or system from intrusions or downtime.

Some of the systems with the highest potential for abuse include the Linux production environments that many businesses use to build their critical applications.

When an issue is discovered on a Linux system, someone has to address it. Generally the only information available is whatever has been stored in a log file somewhere or log management system. This means, for companies using PagerDuty to manage incident response, they will have to execute multiple manual steps in order to open the ticket, find this relevant information, track their fix, and complete the resolution.

# Cmd Integrates with PagerDuty to Make Resolution Seamless

With Cmd’s integration to PagerDuty, an alert generated from within Cmd can be automatically converted to a PagerDuty ticket. All available context and information associated with the alert is tied to the ticket, so the responder has the information they need right at their fingertips. As they conduct their work, Cmd records the work they do in easy-to-navigate logs. Additionally, that audit trail can be associated with a ticket for easy tracking post-resolution.

PagerDuty and Cmd make for a powerful team when it comes to speeding up resolution of potential or actual security incidents within Linux production environments.


With Cmd and PagerDuty integrated, the typical process looks like this:

  • Something anomalous takes place in a Linux production environment
  • An alert is generated within Cmd
  • The Cmd alert can be automatically converted to a PagerDuty ticket
  • The incident responder will have all available context and info tied to the ticket, speeding up incident resolution
  • Cmd records the actions in logs, so there is an audit trail for the entire process

Cmd and PagerDuty let teams:

  • Correlate incident context into a single source of truth
  • Speed up incident resolution
  • Ensure incident resolution processes are tracked for auditing purposes

Companies using Cmd’s PagerDuty integration can also take advantage of other features, such as alerting, reporting, and cloud compliance & auditing management.

Copy link