Slack Integration

Slack is the most popular alert channel for DevOps teams. Pingara's Slack integration delivers rich, formatted notifications directly to your channels with all the context you need to respond quickly.

Prerequisites

Before setting up the integration, you'll need:

• A Pingara Pro account
• Admin access to your Slack workspace
• A Slack channel to receive alerts (e.g., #monitoring-alerts)

Setting Up the Integration

Step 1: Create a Slack App

1. Go to the Slack API portal
2. Click Create New App
3. Choose From scratch
4. Name it "Pingara Alerts" (or any name you prefer)
5. Select your workspace
6. Click Create App

Step 2: Enable Incoming Webhooks

1. In your Slack app settings, go to Incoming Webhooks
2. Toggle Activate Incoming Webhooks to On
3. Click Add New Webhook to Workspace
4. Select the channel (e.g., #monitoring-alerts)
5. Click Allow
6. Copy the Webhook URL — it looks like:

https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX

Security: Treat this URL like a password. Anyone with the URL can post to your channel.

Step 3: Add the Channel in Pingara

1. Go to Settings → Alert Policies → [Your Policy]
2. Click Add Channel
3. Select Slack
4. Paste the Webhook URL
5. Click Save

Step 4: Test the Integration

1. Click Send Test Notification
2. Check your Slack channel for the test message
3. If it arrives, you're all set!

Message Format

Pingara sends richly formatted Slack messages using Block Kit for maximum readability.

Incident Created (Down Alert)

🔴 Monitor Down: api.example.com
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Status:     Investigating
URL:        https://api.example.com/health
Error:      HTTP 503 Service Unavailable
Region:     US East (N. Virginia)
Started:    Jan 15, 2024 2:32 PM UTC

[View Incident]  [View Monitor]

The message includes:

• Color-coded sidebar — Red for down, green for recovery, amber for degraded
• Monitor name and URL — Quick identification
• Error details — Status code, error type, and message
• Affected region — Where the failure was detected
• Timestamp — When the incident started
• Action buttons — Direct links to the incident and monitor in Pingara

Incident Resolved (Recovery Alert)

🟢 Monitor Recovered: api.example.com
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Status:     Resolved
URL:        https://api.example.com/health
Duration:   12 minutes
Resolved:   Jan 15, 2024 2:44 PM UTC

[View Incident]  [View Monitor]

SSL Expiry Warning

⚠️ SSL Certificate Expiring: api.example.com
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

URL:          https://api.example.com
Days Left:    14
Expires:      Jan 29, 2024

[View Monitor]

Performance Degradation

🟡 Monitor Degraded: api.example.com
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Status:       Degraded
URL:          https://api.example.com/health
Latency:      2,340ms (threshold: 500ms)
Region:       EU West (Ireland)

[View Monitor]

Channel Configuration Best Practices

Separate Channels by Environment

Create dedicated channels for different environments:

Configure Slack Notification Settings

For your alert channels, customize Slack's notification behavior:

1. Right-click the channel → Notification Preferences
2. For #prod-alerts: Set to Every new message with sound
3. For #staging-alerts: Set to Mentions only or a digest

Use Thread Replies for Updates

Pingara threads incident updates under the original alert message. This keeps your channel clean:

🔴 Monitor Down: api.example.com       ← Original message
  ├── Status updated: Identified        ← Thread reply
  ├── Status updated: Monitoring        ← Thread reply
  └── 🟢 Resolved (12 min)             ← Thread reply

Multiple Slack Workspaces

If your organization uses multiple Slack workspaces, create a separate webhook for each:

1. Create a webhook in Workspace A → Add as channel in Pingara
2. Create a webhook in Workspace B → Add as another channel in Pingara

Both workspaces will receive alerts for the same monitors.

Troubleshooting

Messages Not Arriving

Check the webhook URL:

• Ensure you copied the full URL including the token
• Verify the URL starts with https://hooks.slack.com/services/

Check the channel:

• Ensure the channel still exists (wasn't deleted or archived)
• Verify the Slack app still has access to post

Check Pingara configuration:

• Ensure the Slack channel is enabled in the alert policy
• Verify the alert policy is linked to the monitor
• Check that the alert trigger is enabled (Down, Recovery, etc.)

Test manually with curl:

curl -X POST -H 'Content-type: application/json' \
  --data '{"text":"Test from Pingara"}' \
  YOUR_WEBHOOK_URL

If this works but Pingara notifications don't arrive, contact support.

Rate Limiting

Slack limits incoming webhooks to 1 message per second. During large-scale outages affecting many monitors simultaneously, some notifications may be slightly delayed.

Webhook URL Expired

Slack webhook URLs can be revoked if:

• The Slack app is uninstalled
• The app's permissions are revoked
• The workspace admin removes the integration

Fix: Create a new webhook and update the URL in Pingara.

Security Considerations

• Rotate webhook URLs periodically — Regenerate if you suspect the URL has been exposed
• Use private channels — Keep alert channels private to your team
• Don't share webhook URLs — Treat them as secrets
• Audit access — Periodically review who has access to alert channels

Next Steps

• Webhook Integration — Build custom integrations
• Alert Channels — Overview of all notification channels
• Setting Up Alerts — Configure alert policies for Slack