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
  1. Integrations
  2. Integrating Custom Alerts & Other Alerting sources

Ingesting Emails as alerts

Last updated 2 months ago

Temperstack's can also ingest emails as a source of alerts and relay it through its notification systems.

This is specifically built to ingest alerts that are created and sent to a specific email address, either as a part of custom alert mechanism coded in your application.

In this integration, each such alert source has a unique email address (which Temperstack generates) where the alert email needs to be directed for the alert to be ingested and relayed to relevant team through the notification system.

This method can also be used to send Alerts generated by other observability tools for which Temperstack does not currently support deep integration or alert listeners .

Steps to Create an Email Integration

  1. Log in to Temperstack.

  2. Go to the Dashboard and select the desired application service.

  3. Navigate to Integration Type, select email and name the integration.

  4. Click on Create Key.

  5. Copy the custom email address provided.

  6. Compose an email containing the alert details and send it to the custom email address.

Example Email Notification

  • To: custom-email@temperstack.com

  • Subject: Alert: Multiple requests are failing

  • Body:

Alert Name: Multiple requests are failing
Status: Alarm
Priority: Critical
Description: Too many requests are failing for X
Metric: 404 Error rate
Resource: Backend API

This email triggers an alert to the team member of the specific application service for acknowledgment, show alert, or resolution.