Temperstack
Main WebsiteFeaturesPricingBlogAbout usRequest a Demo
  • Overview
    • What is Temperstack?
    • Use Cases
  • User Managment
    • Getting started as Admin
      • Inviting Users
      • Mapping multiple services to a Team
      • Single Sign-On (SSO)
      • Customising ALCOM Audit & scanning
    • Getting Started as a User /Responder
    • Managing profile & contact details
  • Integrations
    • Integrating your Observability tools
      • Setting up AWS Integration
        • Multiple AWS Account Integration
        • IAM Setup Guide
          • Creating IAM User: Temperstack with Policy
          • Creating IAM Role: Temperstack with Policy
      • Setting up Microsoft Azure Integration
        • Creating Access for Temperstack in Azure
      • Setting up Google Cloud Platform Integration
        • Creating Access for Temperstack in GCP
      • Setting up Datadog Integration
        • Creating Access for Temperstack in Datadog
        • Managing resources with Datadog
      • Setting up NewRelic Integration
        • Creating Access for Temperstack in NewRelic
        • Managing resources with New Relic
      • Setting up Splunk Integration
        • Creating Access for Temperstack in Splunk
        • Managing resources with Splunk
      • Setting up Appdynamics Integration
        • Creating Access for Temperstack in Appdynamics
        • Managing resources with Appdynamics
      • Setting up Dynatrace Integration
        • Creating Access for Temperstack in Dynatrace
        • Managing resources with Dynatrace
      • Setting up Oracle Cloud Infrastructure
        • Creating Access for Temperstack in OCI
    • Integrating Custom Alerts & Other Alerting sources
      • Webhook Integration
      • Ingesting Emails as alerts
      • Integrating alert listeners from other observability tools
  • Alert routing & Response Managment
    • On-call scheduling and Escalation Policies
    • Setting up Services
    • Alert notification channels
      • Integrating Slack channels
      • Integrating MS Team
    • Mapping resources to Services
      • Rule based resource to Service Mapping
      • Using AI suggested mapping rules
    • Testing Alerting and Notifications
    • Responding to Alerts
  • Monitoring
    • Setting up and maintaining Comprehensive alerting
      • Alerting Templates- metrics & customisation
      • ALCOM and identifying monitoring gaps
      • Programmatically setting up missing alerts in your Observability tool
      • Alert noise Reduction & Optimisation
  • Uptime Monitoring
    • Real time Availability Monitoring
  • Incident analysis & communication
    • External and Internal service Status Pages
      • Instruction to migrate subscribers from Statuspage
  • AI-Powered Issue Resolution
    • AI powered contextual Runbooks
    • Incident command - alert grouping by incident
    • AI Powered Root cause Identification
  • Reporting & Governance
    • Temperstack Dashboard
    • SLO Dashboard
    • MTTA MTTR
  • Billing & Help
    • FAQs
    • Support
Powered by GitBook
On this page
  • Types of Notification Channels
  • Slack channel
  • Group Email Id
  • WhatsApp
  • On-Call Policy
  • Setting up Communication Channels
  1. Alert routing & Response Managment

Alert notification channels

Last updated 4 months ago

Temperstack enables notifications through multiple channels.

Broadcast : Slack and group email ids

Person specific : Phone calls & Whats app

On-call policies facilitate phone call notifications, allowing recipients to promptly acknowledge, resolve, or escalate alerts. Each notification channel plays a vital role in ensuring that critical incidents are promptly addressed and resolved.

Types of Notification Channels

Slack channel

Slack channels serve as a broadcast channel where individuals with access to the slack channel can receive alert notifications. When an alert is raised, the Slack message provides two options: Acknowledge and Resolve. The notification includes details about the alert and the time it was raised, facilitating prompt action by the team members who are assigned in that specific channel.

Group Email Id

Similarly to Slack channels, a group email ID is attached to each service sending email to members belonging to the group email. This email system also offers two options: Acknowledge and Resolve. Recipients receive alerts directly in their email inbox, where they can promptly acknowledge or resolve the alert as needed.

WhatsApp

WhatsApp integration in Temperstack allows you to receive alert notifications directly to the individual team's WhatsApp number. When an alert is raised, the WhatsApp message provides details about the alert, enabling your team to quickly take action by acknowledging or resolving the incident.

On-Call Policy

On-call policies are employed to trigger phone calls, alerting individual on-call team members when incidents occur. When a phone call is received, it provides verbal details about the alert. Recipients are then prompted to take one of three actions: Acknowledge, Resolve, or Escalate. Additionally, escalation policies outline procedures for escalating unresolved issues to higher support levels.

Setting up Communication Channels

  • Navigate to "Temperstack Notifications" at the top menu in your dashboard.

  • From there, select "Application Services."

To set up a communication channel for a new service, follow these steps:

  • Click on the "Add Service" button located at the top right corner of the interface.

  • Check the desired notification channels - email, Slack, and voice - by selecting the corresponding checkboxes. The communication channels will be set up.

To set up a communication channel for an existing service, follow these steps:

  • Navigate to the "Actions" column in the Application Service and click on the "Edit" button.

  • Check or uncheck the options to receive alert notifications on your preferred channels. After making your selections, click on the "Update" button to save the changes.

*To know more on On-Call Policy read - *

On-Call Scheduling and Escalation Policy
Application Service > (Select any one service)