Skip to main content

Alerting

Effective monitoring and alerting are crucial for maintaining reliable integrations. When issues occur - such as a dependent REST endpoint becoming unavailable or an integration's performance degrading significantly - your incident response team needs immediate notification. Proactive monitoring ensures that your team can identify and address integration issues before they impact your customers.

With properly configured monitoring and alerting you can put your mind at ease - no news is good news!

Prismatic alert monitors are configurable.

  • Choose from multiple alert triggers including elevated log levels, execution time thresholds, and failed executions
  • Notify your integration team through various channels:
    • Email and SMS notifications
    • Integration with services like Slack and PagerDuty
    • Custom webhook support for any notification system

Terminology​

  • An alert group defines a set of users and webhooks to notify when an instance exhibits noteworthy or unexpected behavior, such as execution failures.
  • An alert trigger specifies the conditions that initiate an alert monitor. Triggers can be configured for:
    • Performance issues (e.g., exceeded execution time thresholds)
    • Error conditions (e.g., error or warning log messages)
    • Status changes (e.g., successful runs or instance enablement) For a comprehensive list of available triggers, see Alert Triggers.
  • An alert monitor combines an alert group with alert triggers for a specific instance. It defines which conditions should trigger alerts and which groups should be notified.
  • An alert event is generated when an alert trigger's conditions are met. For example, if an instance scheduled to run every 15 minutes fails, an alert event would notify the DevOps team. Subsequent failures would generate new events until the issue is resolved.