Alerts

Configure real-time alerts for pipeline and connector events in Streamkap, with delivery channels like Slack, email, and webhooks.

Alerts provide real-time notifications for critical events in your Streamkap environment, including pipeline state changes, connector actions, latency issues, and system events. Configure delivery channels and customize which alerts you receive to stay informed about your data infrastructure.

Overview

The Alerts page displays a chronological log of all events and notifications in your Streamkap service:

Table Columns

The Alerts table groups alerts by entity and displays the following information:

Timestamp: When the alert was triggered
Status: Alert, Info, or Resolved
Entity: The resource (source, destination, pipeline, transform) that triggered the alert
- Click the name to navigate to the resource detail page
- A dot indicates unread alerts
Message: A brief description of the alert event
- Common events: created, updated, deleted, stopped, resumed, broken, running
The last column has an envelope icon to toggle read/unread status
- Click the envelope icon to mark an unread alert as read
- Click the envelope icon to mark a read alert as unread

Quick Actions

At the top of the page and in the left rail:

Search (Filter loaded alerts…): Filter the loaded alerts by text
By Entity: Filter by entity type (All, Sources, Destinations, Pipelines)
Status: Show Unread, Read, All, or Archived alerts
Mark all read: Button to mark all visible alerts as read
Settings: Opens the Alert Settings page to manage integrations and preferences

Alerts Configuration

Click the Settings button to open the Alert Settings page with two tabs: Integrations and Preferences.

Integrations Tab

Configure integration channels to receive alerts outside the Streamkap app:

Available integrations:

EMAIL

Status: Connect to configure email notifications
Setup: Enter email address(es) to receive alerts

SLACK

Status: Connect via OAuth
Setup:

Click Connect Slack button
You’ll be redirected to Slack, where you can select the channel or user you want to receive the notification.

After clicking the Allow button, you’ll be redirected to the Alert settings page showing the connected channel or user.

You can connect another channel or user by clicking Add Channel button.

GRAFANA

Status: Example shows “Disconnect” button when connected
Setup:

Go to Grafana
Navigate to Alerts & IRM -> Alerting -> Contact points.
Click + Add contact point.
Enter a name for the contact point.
From the Integration list, select Webhook.
In the URL field, copy in your Webhook URL.
(Optional) Configure additional settings.
Click Save contact point.
Copy Webhook URL from Grafana and paste it into the Webhook URL field in the Alert Settings page, then click Save.

Data format:

{
    "data": {
        "action_type": "stopped",
        "datetime": "2026-01-14 21:53:06",
        "entity_id": "685d6baefd035ce5558ad92f",
        "entity_name": "example-source-mongodb",
        "entity_type": "sources",
        "message": "Source: example-source-mongodb has been stopped at 2026-01-14 21:53:06",
        "pending_datetime": "2026-01-14 21:53:06",
        "state": "TRIGGERERD",
        "tenant_id": "c115d79d-5aef-4f6f-8185-a15901c993f8",
        "threshold_value": "None",
        "value": "None"
    }
}

GRAFANA LOKI

Status: Each alert is sent to the Loki push API (/loki/api/v1/push) as one JSON log line.
Use it to send alerts directly to your Loki data source. Grafana contact points send notifications; they do not provide an inbound webhook URL.
Setup for Grafana Cloud:

Sign in to Grafana Cloud, open your stack in the Cloud Portal, and click Details on the Loki card.
Copy the URL (for example https://logs-prod-006.grafana.net) and the User, which is a number.
In your stack, go to Administration > Cloud access policies and create an access policy with the logs:write scope. Click Add token on it and copy the token. Grafana shows it only once.
In the Alert Settings page, click Connect on Grafana Loki, enter the Loki URL, User ID and Token, and click Save.

Fields:
- Loki URL: Required. The base URL of your Loki, or of the gateway in front of it. Must use HTTPS without embedded credentials or a fragment. A URL that already ends in /loki/api/v1/push is accepted; any query parameters are preserved.
- User ID: Optional. With a Token, Streamkap uses HTTP basic authentication, which Grafana Cloud requires. A User ID without a Token is rejected.
- Token: Optional. On its own it is sent as a bearer token, for a self-hosted Loki behind an authenticating proxy. Leave both empty for a Loki that needs no authentication.
- Tenant (X-Scope-OrgID): Optional. Sent as the X-Scope-OrgID header, for a Loki running in multi-tenant mode. Use a single tenant ID of up to 150 characters, following Loki’s tenant ID restrictions.
The token is never shown again after you save. When you edit an authenticated integration, enter the token again. To remove authentication, disconnect the integration and reconnect with both User ID and Token empty.
Alerts reach Loki only for the alert types that have Webhook/API enabled in the Preferences tab.
Alerts are sent from Streamkap’s control plane, not from inside your cloud account. See Streamkap IP Addresses for network guidance and confirm the control-plane egress IPs for your deployment with Streamkap before configuring your firewall.
Labels use a fixed set of names: service_name and source (both streamkap), severity, alert (the alert type, or entity_action for create, update, stop and similar events), state, entity_type and tenant_id. Labels without a value are omitted. Connector IDs and names stay in the log line, so they do not create a separate stream per connector.

Query example (Grafana Explore, Loki data source):

{service_name="streamkap"} | json | data_entity_name="example-source-mongodb"

Data format:

{
  "streams": [
    {
      "stream": {
        "service_name": "streamkap",
        "source": "streamkap",
        "severity": "info",
        "alert": "entity_action",
        "state": "TRIGGERED",
        "entity_type": "sources",
        "tenant_id": "c115d79d-5aef-4f6f-8185-a15901c993f8"
      },
      "values": [["1768427586000000000", "<log line>"]]
    }
  ]
}

The log line is JSON:

{
  "title": "Source example-source-mongodb stopped",
  "message": "Source: example-source-mongodb has been stopped at 2026-01-14 21:53:06",
  "severity": "info",
  "data": {
    "action_type": "stopped",
    "datetime": "2026-01-14 21:53:06",
    "entity_id": "685d6baefd035ce5558ad92f",
    "entity_name": "example-source-mongodb",
    "entity_type": "sources",
    "state": "TRIGGERED",
    "tenant_id": "c115d79d-5aef-4f6f-8185-a15901c993f8"
  }
}

SPLUNK

Status: The system will call the /services/collector/event to send data.
Setup:

Go to Splunk
Navigate Settings > Data inputs and click HTTP Event Collector.
Click New Token button.
In the Input Settings step, do not need to add any index.
Click Submit button.
Copy the Token Value and paste it into the Splunk Token field in the Alert Setting page
Enter the HEC endpoint (Please use the https with port 443) and click Save button.

Data format:

{
  "event": "Destination: Test anil 4 has been resumed",
  "fields": {
    "action_type": "resumed",
    "datetime": "2026-01-07 14:46:46",
    "entity_id": "67e41d2daea865c2ce982b55",
    "entity_name": "Test anil 4",
    "entity_type": "destinations",
    "pending_datetime": "2026-01-07 14:46:46",
    "state": "TRIGGERERD",
    "tenant_id": "82d4a52a-987a-41ab-b199-ac02718a918f",
    "threshold_value": "None",
    "value": "None"
  },
  "source": "Streamkap"
}

DATADOG

Status: The system will call the Event v2 API to send data.
Setup:

Go to Datadog.
Navigate User > API keys and click New Key and create a new API Key.
Navigate User > Application keys and click New Key and create a new Application Key with:

Scope: events_read
Actions API Access: Enabled

Enter your Datadog site (copy it from your Datadog page URL), API Key, and Application Key.
Click Save.

Data format:

{
  "data": {
    "attributes": {
      "attributes": {
        "custom": {
          "action_type": "resumed",
          "datetime": "2026-01-07 14:46:46",
          "entity_id": "67e41d2daea865c2ce982b55",
          "entity_name": "Test anil 4",
          "entity_type": "destinations",
          "pending_datetime": "2026-01-07 14:46:46",
          "state": "TRIGGERERD",
          "tenant_id": "82d4a52a-987a-41ab-b199-ac02718a918f",
          "threshold_value": "None",
          "value": "None"
        },
        "status": "warn"
      },
      "category": "alert",
      "host": "app.streamkap.com",
      "message": "Destination: Test anil 4 has been resumed at 2026-01-07 14:46:46",
      "tags": [
        "source:streamkap"
      ],
      "title": "Destination: Test anil 4 has been resumed"
    },
    "type": "event"
  }
}

PAGERDUTY

Status: The system will call the Event v2 API to send data.
Setup:

Go to PagerDuty.
Navigate Integration > Service integrations and click + New Serivce to create a new service.
In the Integration step, you must to choose the Events API V2, then click Create Service button.
Copy the Integration Key and paste it into the Integration Key field in the Alert Setting page
Click Save.

Data format:

{
  "payload": {
      "summary": "Destination: Test anil 4 has been resumed at 2026-01-07 14:46:46",
      "source": "https://app.streamkap.com",
      "severity": "error",
      "custom_details": {
        "action_type": "resumed",
        "datetime": "2026-01-07 14:46:46",
        "entity_id": "67e41d2daea865c2ce982b55",
        "entity_name": "Test anil 4",
        "entity_type": "destinations",
        "pending_datetime": "2026-01-07 14:46:46",
        "state": "TRIGGERERD",
        "tenant_id": "82d4a52a-987a-41ab-b199-ac02718a918f",
        "threshold_value": "None",
        "value": "None"
      }
  }
}

CUSTOM WEBHOOK

Type: Webhook
Status: Connect to configure
Setup: Provide incoming webhook URL and the authentication
Available authetication:
- NONE
- BASIC: Need to provide username and password
- BEARER: Need to provide the bearer token

Preferences Tab

Configure which alert types you want to receive and through which channels:

Alert categories and their enabled channels:

Destination Actions

Events: Destination connector created, updated, deleted, stopped, resumed
Default channels: (expand to configure)

Pipeline Actions

Events: Pipeline created, updated, deleted, stopped, started
Enabled channels: Email

Recovery - Pipeline Is Running

Events: Pipeline recovered from error state and is now running
Enabled channels: Email, In Streamkap App, Chat (eg. Slack), Webhook/API

Recovery - Pipeline Latency less than 10 minutes

Events: Pipeline recovered from latency less than 10 minutes
Enabled channels: Email, In Streamkap App, Chat (eg. Slack), Webhook/API

Source Actions

Events: Source connector created, updated, deleted, stopped, resumed
Enabled channels: Email, In Streamkap App, Chat (eg. Slack), Webhook/API

Triggered - Pipeline Dead Letter Queue

Events: Messages sent to dead letter queue due to processing errors
Enabled channels: Email, In Streamkap App, Chat (eg. Slack), Webhook/API
Critical alert for data quality issues

Triggered - Pipeline JSON Column

Events: Destination has any json columns
Enabled channels: Email, In Streamkap App, Chat (eg. Slack), Webhook/API
Critical alert for data quality issues

Triggered - Pipeline Latency greater than 10 minutes

Events: Pipeline processing latency exceeds threshold
Enabled channels: Email, In Streamkap App, Chat (eg. Slack), Webhook/API
Important for monitoring real-time performance

Triggered - Pipeline Not Running

Events: Pipeline stopped unexpectedly or failed to start
Enabled channels: Email, In Streamkap App, Chat (eg. Slack), Webhook/API
Critical alert for system availability

Setting Up Alerts

Navigate to Alerts Page

Click Alerts in the sidebar to view your alerts.

Open Alert Settings

Click the Settings button in the top right corner.

Configure Integration Channels

In the Integrations tab:

Click Connect next to each integration you want to enable
Follow the setup wizard for each channel:
- Email: Enter email addresses
- Slack: Authorize OAuth connection
- Teams/Discord/Mattermost/Grafana: Provide webhook URLs
- Grafana Loki: Provide the Loki URL and, for Grafana Cloud, the user ID and token
Test the connection to ensure proper configuration

Customize Alert Preferences

Switch to the Preferences tab:

Click on each alert category to expand it
Select which channels should receive each type of alert
Enable channels by turning on their switches (Email, Webhook/API, In Streamkap App, Chat (eg. Slack))
Disable alerts you don’t need by turning off all their channels

Save Configuration

Your changes are saved automatically as you configure each setting.

Alert Types

Connector Events

Source and Destination Actions

Created
Updated (configuration changed)
Deleted
Stopped/paused
Resumed/started

Pipeline Events

State Changes

Created
Updated (settings modified)
Deleted
Started
Stopped
Broken (encountered error)
Recovered (returned to running state)

Performance Alerts

Pipeline latency exceeds 10 minutes
Pipeline dead letter queue triggered
Pipeline not running (unexpected stoppage)

Service Events

Service configuration changes
Service status updates
Resource quota alerts

Alert title and severity
Resource name and type
Event description
Timestamp
Direct link to resource in Streamkap

Slack Integration

Post alerts to Slack channels with rich formatting:

Colored indicators based on severity
Resource details and links
Inline actions (when applicable)
Thread support for related alerts

Webhook Integrations

Teams, Discord, Mattermost, and Grafana receive alerts via webhooks with structured payloads including:

Event metadata
Resource information
Timestamp
Severity level
Direct link to Streamkap

Managing Alerts

Marking Alerts as Read

Click the envelope icon on an individual alert to toggle its read/unread status
Click Mark all read at the top to mark all visible alerts as read
Unread alerts are marked with a dot and remain visible when the Unread status filter is selected

Filtering Alerts

Search: Type in the search box to filter the loaded alerts by text
By Entity: Show only specific resource types
Unread: Select the Unread status filter to hide alerts you’ve already seen

Pagination

View 20, 50, or 100 alerts per page using the dropdown
Navigate between pages using Previous/Next buttons or page numbers

Best Practices

Configure Critical Alerts First: Set up notifications for pipeline failures, dead letter queues, and high latency alerts
Use Multiple Channels: Configure both email and chat integrations for redundancy
Customize by Environment: Use different Slack channels or email lists for production vs. development services
Review Regularly: Check the Alerts page periodically to identify patterns or recurring issues
Test Integrations: After setting up webhooks, trigger a test alert to verify delivery
Tune Thresholds: Adjust latency thresholds and alert frequency to reduce noise while maintaining awareness

Troubleshooting

Not Receiving Alerts

If alerts aren’t being delivered:

Check Integration Status: Ensure the integration shows “Connected” in the Integrations tab
Verify Webhook URLs: Copy and test webhook URLs in a tool like curl or Postman
Check Email Spam: Email alerts may be filtered as spam initially
Review Preferences: Confirm the alert type has the correct channels enabled
Test Connection: Disconnect and reconnect the integration

Too Many Alerts

If you’re overwhelmed with notifications:

Disable Low-Priority Alerts: Uncheck channels for informational alerts in Preferences
Use Filters: Set up separate channels for different severity levels
Adjust Thresholds: Consider increasing latency thresholds if appropriate
Mute Specific Types: Disable alerts for routine operations like connector updates

Slack Not Posting

If Slack integration isn’t working:

Re-authorize: Disconnect and reconnect the Slack integration
Check Permissions: Ensure the Streamkap app has permission to post in your workspace
Verify Channel: Confirm the target Slack channel still exists
Test OAuth Token: OAuth tokens may expire; reconnecting refreshes the token

Grafana Loki Not Receiving Alerts

If alerts don’t appear in Loki:

Enable the channel: In the Preferences tab, turn on Webhook/API for the alert types you want in Loki.
Widen the query: Search {service_name="streamkap"} over the last hour, with no other filters.
Check credentials: For Grafana Cloud, User ID is the numeric Loki user and the token needs the logs:write scope. After editing the integration, enter the token again.
Check network access: Loki must be reachable from Streamkap’s control plane. Review Streamkap IP Addresses and confirm the control-plane egress IPs with Streamkap; allowing traffic only from your own cloud account is insufficient.

Logs - View detailed system logs for debugging
Pipelines - Manage data pipelines
Sources - Configure source connectors
Destinations - Configure destination connectors
Projects - Manage Streamkap projects

Alerts

Overview

Table Columns

Quick Actions

Alerts Configuration

Integrations Tab

Preferences Tab

Setting Up Alerts

Alert Types

Connector Events

Pipeline Events

Service Events

Alert Channels

In-App Notifications

Email Notifications

Slack Integration

Webhook Integrations

Managing Alerts

Marking Alerts as Read

Filtering Alerts

Best Practices

Troubleshooting

Not Receiving Alerts

Too Many Alerts

Slack Not Posting

Grafana Loki Not Receiving Alerts