Set Up Monitoring Alerts for Slack, Chatwork, and LINE

Get Instant Downtime Alerts in the Tools You Already Use

The most sophisticated monitoring setup is worthless if nobody sees the alerts. Email notifications get buried. Relying on a dashboard somebody checks "when they remember" is not a strategy. The solution is routing alerts directly to the chat tools your team lives in every day.

This guide walks through setting up Slack, Chatwork, and LINE alerts with Miterl.

Notification Targets Are Created as Alert Contacts

In Miterl, notification targets -- Slack, Chatwork, LINE, email -- are registered as alert contacts in the dashboard. Create a contact once, then attach it to any monitor to start receiving alerts.

You cannot create the notification target itself through the API, but you can list your existing alert contacts and their IDs via the API. Pass those IDs to a monitor's alert_contact_ids to control, programmatically, which monitor routes to which destination.

Slack Alert Setup

Slack is the go-to for most development teams. Miterl connects via a standard Incoming Webhook.

Steps:

1. In your Slack workspace, open the target channel and add the Incoming Webhooks app
2. Copy the generated Webhook URL
3. In Miterl's dashboard, open Alert Contacts, select Slack, and paste the URL to create the contact
4. On the monitor's edit screen, attach the Slack contact as a notification target

Chatwork Alert Setup

Chatwork is widely used by agencies and their clients in the Japanese market. Miterl integrates natively with the Chatwork API.

Steps:

1. Go to Chatwork's "Service Integration" settings and generate an API token
2. Find the Room ID of your target room (the number after #!rid in the URL)
3. In Miterl's dashboard, open Alert Contacts, select Chatwork, and enter the API token and Room ID to create the contact
4. On the monitor's edit screen, attach the Chatwork contact as a notification target

Wiring Contacts to Monitors via the API

Alert contacts created in the dashboard can be listed -- along with their IDs -- via the API.

# List your existing alert contacts and their IDs
curl -X GET https://miterl.com/api/v1/alert-contacts \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json"

# Example response:
# {"data":[{"id":1,"type":"slack","name":"Engineering Alerts","is_active":true},
#          {"id":2,"type":"chatwork","name":"Client A Alerts","is_active":true}]}

Pass those IDs as alert_contact_ids (an array of integers) when you create or update a monitor.

# Attach the Slack (1) and Chatwork (2) contacts to a monitor
curl -X POST https://miterl.com/api/v1/monitors \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Client A Website",
    "type": "http",
    "url": "https://client-a.example.com",
    "interval_seconds": 300,
    "alert_contact_ids": [1, 2]
  }'

LINE Alert Setup

LINE Notify delivers push notifications directly to your phone. This is ideal for high-priority sites where you need to know about outages even when you are away from your desk.

Steps:

1. Log in to LINE Notify and generate a token
2. Choose a notification target -- either a group or "1-on-1 with LINE Notify"
3. In Miterl's dashboard, open Alert Contacts, select LINE, and enter the token to create the contact

Routing Alerts by Purpose: A Strategy for Agencies

When managing multiple client sites, sending every alert to a single channel creates noise. Instead, route alerts based on audience and urgency.

With Miterl, you can attach multiple alert contacts to a single monitor (via the API, just pass several IDs in alert_contact_ids). For example, send alerts to Slack for your engineering team and simultaneously to LINE for on-call escalation.

Always Test Your Notifications

After configuring a contact, send a test notification before trusting it in production. Miterl's dashboard includes a "Send Test" button for each configured alert contact -- use it.

Combining Chat Alerts with Webhooks

Slack, Chatwork, and LINE alerts are primarily about notifying people. Webhooks serve a different role: notifying systems for automated processing. For example, triggering an auto-recovery script or creating a ticket in an incident management tool (PagerDuty, Opsgenie) when a monitor goes down.

You can attach both a Slack contact (team notification) and a webhook destination (automated processing) to the same monitor simultaneously. For practical automation examples, see "Webhook Integration for Uptime Monitoring."

Notification Setup Checklist

After configuring your alert contacts, run through this checklist before relying on them in production:

• Send a test notification and confirm it arrives at the correct destination
• Verify alerts are not buried during off-hours (nights, weekends, holidays)
• Set a flapping threshold so short up/down cycles do not flood your channels
• Configure a maintenance window to suppress alerts during planned downtime

For detailed configuration options, see the documentation. To explore other Miterl features, visit use cases or browse the FAQ for answers to common questions.