Uptime Kuma now has a Flowtriq
notification provider

Back to Blog

What Happened

We submitted a pull request to Uptime Kuma adding Flowtriq as a native notification provider under the Incident Management category. It was reviewed and merged on June 28, 2026.

Uptime Kuma is the most popular open-source uptime monitoring tool, with over 60,000 GitHub stars. It monitors HTTP, TCP, DNS, and other service endpoints and notifies you when something goes down. With Flowtriq as a built-in notification provider, downtime events are forwarded directly to your Flowtriq instance for correlation with DDoS detection data.

How to Set It Up

1. In your Uptime Kuma dashboard, go to Settings > Notifications.
2. Click Setup Notification.
3. Select Flowtriq from the notification type dropdown (listed under Incident Management).
4. Enter your Webhook URL (your Flowtriq webhook endpoint).
5. Optionally enter your API Key for authentication.
6. Click Test to verify, then save.

Once configured, every monitor state change (up, down, pending) triggers a POST to your Flowtriq webhook with the monitor name, status, heartbeat data, and response details.

What Gets Forwarded

The notification provider sends a structured JSON payload containing three objects:

• Monitor details: name, URL, type (HTTP, TCP, DNS, etc.), hostname, port, and the monitor's configured interval
• Heartbeat data: current status, response time in milliseconds, timestamp, and any error message
• Message: human-readable notification text (e.g., "Website is DOWN")

{
  "monitor": {
    "name": "API Gateway",
    "url": "https://api.example.com/health",
    "type": "http",
    "hostname": "api.example.com",
    "port": 443
  },
  "heartbeat": {
    "status": 0,
    "time": "2026-07-23T15:42:30.000Z",
    "msg": "connect ETIMEDOUT",
    "ping": null
  },
  "msg": "[API Gateway] [🔴 Down] connect ETIMEDOUT"
}

Flowtriq's inbound webhook normalizes this payload and places it on your event timeline. If a DDoS attack was detected around the same timestamp targeting the same IP or hostname, the correlation is immediate.

Why This Matters

The first question during any outage is "why." Is it a code deployment gone wrong? A database overload? Or is someone flooding the server with traffic?

Without correlation, answering that question means checking multiple systems. Your uptime monitor says the service is down. Your DDoS detection system may or may not have detected an attack. You have to manually line up the timestamps and make the connection.

With the Flowtriq notification provider, Uptime Kuma pushes downtime events directly into the same timeline where DDoS attacks appear. If your web server goes down at 15:42 and Flowtriq detected a 2 Gbps UDP flood starting at 15:41, you see both events together. The root cause is obvious without a second dashboard.

This also works in the other direction. If Uptime Kuma reports a service down and there is no corresponding DDoS event in Flowtriq, you can immediately rule out a network attack and focus on application-level causes. Knowing what it is not is just as useful as knowing what it is.

The Contribution

The PR touched six files across the Uptime Kuma codebase:

• server/notification-providers/flowtriq.js - Backend provider that POSTs monitor status, heartbeat, and details to the Flowtriq webhook
• src/components/notifications/Flowtriq.vue - Vue form component for configuring the webhook URL and API key
• server/notification.js - Provider registration in the backend notification list
• src/components/notifications/index.js - Frontend component registration
• src/components/NotificationDialog.vue - Category assignment (Incident Management)
• src/lang/en.json - English translation strings

The implementation follows Uptime Kuma's standard notification provider pattern. The backend provider handles JSON serialization and HTTP POST with optional API key authentication. The Vue component provides the configuration form with URL and API key fields.

Back to Blog

Related Articles