All Integrations
AlertingEmail Notification

Email Alerts Integration

Receive rich HTML incident emails with embedded metric charts, AI summaries, and direct deep links to TigerOps investigations. Stay on top of incidents even away from your chat tools.

Setup

How It Works

01

Configure Email Recipients

In TigerOps, add individual email addresses or distribution group addresses as notification targets. Verify each address with a one-click confirmation email.

02

Set Delivery Rules per Severity

Define which severity levels trigger email notifications. Critical incidents can email the entire on-call distribution list while warnings go only to team leads.

03

Customize Email Templates

Choose from pre-built HTML email templates or create your own with TigerOps template variables. Include metric snapshots, AI summaries, and branded headers.

04

Alerts Arrive with Full Context

Every incident email contains the AI summary, affected services, metric charts, trace links, and direct action buttons — everything needed to triage without opening TigerOps.

Capabilities

What You Get Out of the Box

Rich HTML Email Templates

Incident emails use responsive HTML templates with severity color coding, service badges, and structured data sections — readable on any email client or mobile device.

Embedded Metric Charts

TigerOps embeds a snapshot chart of the anomalous metric directly in the email body, so recipients see the spike or drop without clicking through to the dashboard.

AI Summary in Every Email

Each incident email leads with an AI-generated plain-language summary: what service is affected, what the anomaly looks like, and what the probable cause is.

Deep Links to Investigation

Action buttons in every email link directly to the TigerOps incident timeline, the relevant trace, the impacted dashboard, and the AI runbook suggestions.

Resolution and Digest Emails

When an incident resolves, TigerOps sends a resolution email with duration, root cause, and a link to the postmortem. Daily digest emails summarize all alert activity.

Per-Team Distribution Lists

Map alert policies to different email recipients or distribution lists. Infrastructure alerts go to [email protected], app errors to [email protected].

Configuration

Email Alert Policy Config

Configure recipients, severity thresholds, and template options for email notifications.

email-alerts.yaml
# TigerOps — Email Alert Configuration

integrations:
  email:
    smtp_relay: "ses"          # Options: managed, smtp, ses, sendgrid
    from_address: "[email protected]"
    from_name: "TigerOps Monitoring"

alert_policies:
  - name: "Critical Incident Emails"
    severity: [critical]
    notification_channels:
      - type: email
        recipients:
          - "[email protected]"
          - "[email protected]"
        template: "critical-incident"
        include_metric_chart: true
        include_ai_summary: true
        include_trace_link: true
        send_resolution: true

  - name: "Daily Warning Digest"
    severity: [warning]
    notification_channels:
      - type: email
        recipients:
          - "[email protected]"
        mode: digest
        digest_schedule: "0 9 * * *"   # 9am daily
        template: "digest-summary"

email_templates:
  - id: "critical-incident"
    subject: "[CRITICAL] {{service_name}} — {{incident_title}}"
    header_color: "#ef4444"
  - id: "digest-summary"
    subject: "TigerOps Daily Alert Digest — {{date}}"
    header_color: "#f59e0b"
FAQ

Common Questions

Does TigerOps send emails directly or through an SMTP relay?

By default TigerOps sends emails through its managed sending infrastructure (using dedicated sending domains for high deliverability). You can also configure a custom SMTP relay or Amazon SES credentials if your organization requires it.

Can I prevent alert floods if many incidents fire simultaneously?

Yes. TigerOps groups related alerts into a single incident and sends one email per incident, not one per alert. You can also enable digest mode, which batches all active incidents into a single periodic summary email.

Will email recipients receive a second email when an incident resolves?

Yes, if resolution notifications are enabled (the default). The resolution email includes the incident duration, a one-line AI root cause summary, and a link to the postmortem. Resolution emails can be disabled per alert policy.

How do I unsubscribe a recipient from TigerOps alert emails?

Every TigerOps alert email contains a one-click unsubscribe link as required by CAN-SPAM. You can also remove recipients from the TigerOps integrations panel at any time. Unsubscribes are honored within minutes.

Are the metric chart images in emails accessible to all email clients?

TigerOps embeds charts as base64-encoded inline images and also provides a fallback text table of metric values for email clients that block remote or inline images. All charts include alt text for screen reader accessibility.

Get Started

Send Rich Incident Emails Automatically

No credit card required. Add recipients in minutes. AI summaries and charts in every email.