RudderStack Docs – Debugging & Monitoring

Releases: PagerDuty and incident.io Alert Channels

Wed, 15 Jul 2026 00:00:00 +0000

You can now deliver RudderStack’s Configurable Alerts directly into PagerDuty and incident.io — the two tools engineering teams use to run on-call and incident response — alongside the existing Slack, Microsoft Teams, email, and webhook channels. When a pipeline breaks, the alert lands where your on-call attention already lives instead of getting buried in a channel or inbox.

This adds two new delivery destinations for the alerts RudderStack already detects. It does not change what RudderStack monitors or how alert thresholds work — only where those alerts can be sent.

Not to be confused with the PagerDuty destination

This feature sends RudderStack’s operational health signals out to your incident tooling. It is different to the PagerDuty destination, which sends your event data into PagerDuty.

Why route alerts to your incident tools?

A broken pipeline is a business-critical failure, not a cosmetic one. It can silently drop or corrupt the data feeding your analytics, ML models, and downstream marketing and product decisions — and the damage is often invisible until someone notices the numbers are wrong days later.

The problem is that a Slack message or an email is easy to miss. A page is not.

PagerDuty guarantees the right on-call human is actually notified — loudly, via phone, SMS, or push — and auto-escalates if nobody acknowledges.
incident.io coordinates the response once people are aware, spinning up an incident channel, assigning roles, and auto-capturing a timeline that becomes the postmortem.

Meeting your team where its on-call attention already lives turns a RudderStack failure from a buried notification into a real page. For a platform whose promise is data reliability, that closes a direct trust gap.

What you can route

RudderStack’s existing alert engine already detects the failures that matter most (this set is unchanged):

A destination starts rejecting or failing to receive events (bad credentials, downtime, network errors)
A warehouse sync aborts, or pre-sync processing fails
A transformation starts erroring and dropping events
Event volume drops suspiciously versus the same hour last week
A source violates its Tracking Plan (data arriving in the wrong shape)
A Reverse ETL sync fails partially or fatally
A Profiles run fails

Any of these can now land as a PagerDuty incident (with escalation policies, on-call schedules, and phone/SMS/push paging) or as an incident.io alert (which can trigger an incident channel, role assignment, and an auto-built postmortem timeline).

Key features

PagerDuty routing with real paging and escalation: Route any RudderStack alert into a PagerDuty service so the right on-call engineer is paged and alerts auto-escalate if unacknowledged.
incident.io routing with response coordination: Deliver alerts into incident.io to kick off an incident channel, assign roles, and capture a timeline for the postmortem.
Setup in minutes: Configuration is minimal — for PagerDuty, create a service with an Events API v2 integration and paste the 32-character integration/routing key. For incident.io, create an HTTP alert source and paste the secret API key plus the (non-secret) alert source config ID.
The same guardrails as every channel: Only org admins can configure workspace-level channels; alerts are de-duplicated (at most one notification per resource, per alert type, per channel every 24 hours, so on-call isn’t spammed); you can’t disable your last remaining production channel, so you’re never flying blind; and a test alert button confirms the wiring before you rely on it.

Get started

PagerDuty and incident.io alert channels are available on the RudderStack Growth and Enterprise plans and are configured at the workspace level from your RudderStack dashboard:

Go to Data Governance > Alerts in your RudderStack dashboard.
Choose the PagerDuty or incident.io channel.
For PagerDuty, paste your 32-character Events API v2 integration key. For incident.io, paste your HTTP alert source API key and alert source config ID.
Click the test alert button to confirm the connection, then save.

See the Configurable Alerts guide for full setup instructions for both channels.

For vendor-side context, see PagerDuty’s own Events API v2 documentation and incident.io’s Custom HTTP alert source documentation.

Releases: RudderStack Assistant

Mon, 15 Jun 2026 00:00:00 +0000

We are excited to announce the RudderStack Assistant, a browser extension for Chrome and Firefox that transforms how you debug and validate your JavaScript SDK implementation. It provides instant visibility into your RudderStack setup directly in your browser.

Why RudderStack Assistant?

Debugging SDK implementations has traditionally required waiting 1-5 minutes for events to appear in the dashboard, piecing together information from browser’s developer tools, or filing support tickets for complex issues. The RudderStack Assistant eliminates these friction points by providing real-time feedback in under one second.

Key features

Real-time event monitoring: See events the moment they fire with full payload inspection, filtering by event type, and visual status indicators.
SDK health dashboard: Instantly view SDK version, write key, data plane URL, installation type (CDN vs NPM), and CSP compatibility.
Destination and plugin visibility: Monitor device-mode destination status and debug configuration issues without leaving your browser.
SDK injection: Test RudderStack JavaScript SDK on any website without code changes — ideal for evaluation, prototyping, and demos.
One-click debug export: Export comprehensive debug data including SDK state, events, and logs to streamline support communication.

Installation

All data processing occurs locally in your browser. The extension does not transmit captured events or SDK information to external servers.

Get started

Install the extension from the Chrome Web Store or Firefox Add-ons.
Navigate to any website with the RudderStack JavaScript SDK installed.
Open the extension to instantly view your SDK configuration, health status, and real-time events.
Use the Events tab to monitor event payloads as they fire, or the Overview tab to inspect destinations and plugins.
Export debug data with one click to share with your team or RudderStack support.

Resources

See the following guides for detailed instructions on using the extension:

Releases: P95 Latency Alerts for Event Stream Destinations: General Availability

Fri, 27 Feb 2026 00:00:00 +0000

P95 latency alerts for Event Stream cloud destinations are now Generally Available for all Enterprise customers.

You can now configure P95 latency thresholds for your Event Stream cloud destinations and receive alerts whenever event delivery slows beyond acceptable limits. For example, if you set a P95 latency threshold of 15 minutes and 95% of events aren’t delivered within that window, RudderStack triggers an alert on your configured delivery channels — Slack, email, Microsoft Teams, or a custom webhook.

This helps you catch delivery delays early, troubleshoot proactively, and keep stakeholders informed before issues escalate.

What’s new

Generally available: P95 latency alerts are no longer in beta. They are fully supported and available for all Enterprise customers.
Expanded access: Previously, only Admins could view the P95 latency metric. Now, any user subscribed to P95 latency alerts for a destination can also view its latency metrics directly in the Events tab.

P95 latency alerts apply only to Event Stream destinations connected to sources in cloud mode.

They do not apply to Reverse ETL connections, warehouse destinations, and device mode connections.

See the following guides for more details:

Set up P95 latency alerts: Configure alert thresholds for your destinations
View the P95 latency event metric: View and interpret the P95 latency metric for your destination

Screenshots

Configure P95 latency alerts in the RudderStack dashboard:

View the P95 latency metric for a destination:

View the P95 latency for events coming from a particular source:

Releases: Bot Management

Mon, 23 Feb 2026 00:00:00 +0000

We are excited to announce Bot Management, a data governance feature that detects, flags, and drops bot traffic on web sources before it enters your data pipelines. By identifying and managing bot events early in your data flow, you can significantly improve data quality and reduce unnecessary costs.

Why Bot Management?

Managing bot traffic has traditionally required implementing custom detection logic in downstream systems, leading to inconsistent bot detection across your analytics stack and inflated costs from processing non-human events. Bot Management eliminates these challenges by providing a centralized, reliable filtering layer that standardizes bot detection across your web sources.

Key features

User agent-based detection: Automatically identifies bot events using predefined bot patterns to detect common bots, crawlers, and automated traffic.
Flexible event management: Choose to flag bot events for downstream analysis or drop them entirely at the gateway to prevent unnecessary processing costs.
Workspace and source-level configuration: Set global bot management settings for all web sources or apply custom configurations for individual sources based on your specific requirements.
Real-time bot metrics: Monitor bot event volume patterns at the source level through the source Events view. For more details, see View Bot Event Metrics.
Cost optimization: Drop bot events at the gateway to reduce billable event volume and prevent unnecessary costs across pipelines, data stores, and analytics tools.

Get started

Bot Management is available in all RudderStack paid plans. You can get started with just a couple of clicks — navigate to Govern > Bot Management in your RudderStack dashboard and enable bot detection for your workspace.

See the Bot Management documentation for detailed instructions.

Resources

See the following guides for detailed instructions on using this feature:

Screenshots

Bot management view in the RudderStack dashboard

Bot management global setting

Source-level bot event management

Bot event metrics in the source page

Releases: Event Stream Destination Latency Metrics

Thu, 27 Mar 2025 00:00:00 +0000

For data teams, managing stakeholder expectations is critical - they want to see the right data arrive on time.

For data engineers running RudderStack, a variety of factors can impact how quickly data is delivered to destinations. Some variables, like complexity of Transformations attached to a destination, are within your control. In many cases, though, latency can increase due to external factors like sudden traffic spikes or degraded performance of a destination API.

Previously, it was difficult for data engineers to troubleshoot data delays for specific destinations.

Now, RudderStack Org Admins can see granular latency metrics for every cloud destination, giving them visibility into delivery latency and equipping them to better manage stakeholder expectations.

These metrics include:

P95 latency for the selected time window: 95% of data is delivered within or faster than this time. For example, if P95 latency for the last two hours is 9 seconds, that means that 95% of events delivered over the last two hours were delivered within 9 seconds or less.
Latency trend: The latency trend shows P95 latency at intervals over the selected time window. This view is helpful for isolating the timing and impact of increased or decreased latency.

See our P95 Latency Event Metrics documentation for more information on this feature.

Screenshots

Releases: Warehouse Sync Metrics

Wed, 26 Mar 2025 00:00:00 +0000

Loading event data into a data warehouse is one of the most common use cases for data teams running RudderStack. A majority of the time sync jobs run without issues, but factors like significant spikes in volume, corrupted data, and other issues out of the data team’s control can make sync jobs run longer than normal. This latency can impact scheduled jobs, reporting, and other use cases for consumers of the data.

Previously, troubleshooting potential latency problems required manually scrolling through a list of sync jobs. Not only was that time consuming, but there was no way to see trends over time.

With warehouse sync metrics, you can see max sync duration over multiple time windows (2 hours, 1 day, 7 days, and 30 days), and see the duration of each individual sync job within the selected window.

With these observability tools, you can more quickly isolate potential problems with data delivery and understand how changes in your data might impact load performance over time.

See our Event Metrics documentation for more information on this feature.

Screenshots

Releases: Destination Event Details

Mon, 10 Mar 2025 00:00:00 +0000

Data engineers running RudderStack often get questions from their stakeholders about potential problems with event delivery to a specific destination.

Previously, the events view on destinations was limited, showing only a basic chart and failure responses by top-level event type.

Now, you can see a full list of events that RudderStack has attempted to deliver to each destination, including diagnostic data for:

Successful deliveries
Time of last successful delivery
Failures
Time of last failure

You can also drill into individual events to see granular failure information, including sample payloads.

Note that table shows post-transformation event names, which ensures you are seeing the exact events that RudderStack is delivering to your destination, even if you have modified the event name or have generated new events in a user transformation.

See our Event Metrics documentation for more information on this feature.

Screenshots

Releases: Transformation Failure Alerts

Fri, 07 Mar 2025 00:00:00 +0000

You can now configure dedicated alerts for Transformation failures, giving you the ability to take immediate action when problems arise.

Transformation failures can happen for multiple reasons:

Unexpected data causing errors
Testing not covering all use cases across production data, or
A source with new data is connected to the destination.

Previously, these failures would materialize as cloud destination failure alerts, making it difficult to trace problems. With dedicated transformation failure alerting, you’ll be notified if there is an unexpected problem and can take action immediately.

With this feature, you can configure a global failure rate threshold (applicable for all transformations) and specific thresholds for individual transformations.

See Transformation failure alerts for more information on this feature.

Screenshots

Releases: Events Tab 2-hour Time Window

Fri, 14 Feb 2025 00:00:00 +0000

Previously, the Events tab view in the Sources, Transformations, and Destinations configured in RudderStack defaulted to a 1-day time window.

Now, the Events tab defaults to a 2-hour time window, giving you much more granular visibility into data flow over the last few hours.

In the 2-hour view, data flow is shown in 5-minute increments, helping you:

Review recent spikes or drops in traffic and events with higher precision.
Troubleshoot potential issues as soon as they arise.
Quickly validate if the fixes are having the desired effect.

See our Event Metrics documentation for more information on this feature.

Screenshots

Releases: Iterable Observability Enhancements

Wed, 08 Jan 2025 00:00:00 +0000

Today, we released some important observability and error reporting enhancements for the Iterable destination, applicable to both Event Stream (cloud mode) and Reverse ETL connections.

With these changes, faulty events previously misclassified with an HTTP 200 status code but failed to deliver to Iterable are now correctly marked with the relevant error codes and Iterable API responses.

You will see improved error reporting in the RudderStack dashboard for:

Events sent to Iterable with non-existent user IDs.
Validation errors due to data type mismatch for the fields passed in the events.
Disallowed event names.

As a result of these changes, you may observe an increase in reported errors (based on traffic, event volume, and issues with sent events), giving you improved visibility and enabling faster resolution.

Contact the RudderStack team for more information on this enhancement.

Releases: Warehouse Observability Enhancements

Wed, 20 Nov 2024 00:00:00 +0000

RudderStack’s latest warehouse observability enhancements give you detailed insights into why the data going to a warehouse destination was discarded, especially in cases where there is a data type mismatch and the event data does not conform to the Warehouse Schema.

How the feature works

RudderStack discards any event data going into a warehouse destination that does not strictly conform to the Warehouse Schema spec and cannot be fixed.

In such cases, RudderStack puts the discarded records into a rudder_discards table along with a reason. With the latest observability enhancements, the reasons will give more insights on exactly why the data was discarded.

Some examples are shown below:

incompatible schema conversion from string to boolean
incompatible schema conversion from string to int
incompatible schema conversion from datetime to string
incompatible schema conversion from bigint to float

Releases: Configurable Alerts for Profiles

Thu, 08 Aug 2024 00:00:00 +0000

RudderStack now supports setting up notifications for any failures in your Profiles project runs. This helps you troubleshoot the issues and take remedial actions on time.

To use this feature:

Navigate to Settings > Workspace in your RudderStack dashboard and go to the Alerts tab.
Click the Profiles tab and toggle on the Run failures setting.

Read more about this feature in the Configurable Alerts guide.

Releases: Configurable Alerts Enhancement

Tue, 05 Mar 2024 00:00:00 +0000

RudderStack now supports smart alerting capabilities that let you set up timely notifications for critical data issues, helping you take necessary actions before they escalate into major problems.

With this alerting feature, you can:

Configure alerts for event delivery failures, warehouse pre-sync or sync failures, and tracking plan violations.
Set failure thresholds at a workspace and resource level, so you are notified only when absolutely necessary.
Break alerting silos by setting up alert delivery channels of your choice like email, webhook, Slack, PagerDuty, or any other tool of your choice.

Read more about this feature in our Configurable Alerts guide.

Releases: Feature Launch: Health Dashboard for Data Quality Monitoring and Alerting

Thu, 01 Feb 2024 00:00:00 +0000

Today, we’re introducing the Health Dashboard, the final tool in our Data Quality toolkit. It provides a centralized place to monitor data quality and manage alerts across your entire stack.

With the Health Dashboard, you can drive data trust and ensure that every strategic decision, from marketing campaigns to product development, is based on accurate and reliable information. It exposes the key metrics related to your pipelines like:

Event ingestion metrics
Event delivery metrics
Warehouse load metrics
Tracking plan violations

You can also set up timely notifications for critical issues so you can take appropriate action immediately. You can configure thresholds for key alerts by source and destination, and deliver alerts to your system of choice like email, webhook, Slack, or any other tool of your choice.

For more information on this feature, see our Health Dashboard for Data Quality Monitoring and Alerting launch blog.

Releases: Health Dashboard for Pipelines and Tracking Plans Observability

Thu, 16 Nov 2023 00:00:00 +0000

We have released the Health dashboard to help you get better observability into your Event Stream pipelines and tracking plans.

This dashboard gives you visibility into the event delivery and failures for all the Event Stream destinations in your workspace. You can filter your destinations by type (Cloud or Warehouse) or view metrics for only the destinations that have event failures.

In the Tracking Plans tab, you get a list of all sources connected to a tracking plan in your workspace along with metrics for validated events and violations.

We’re also planning to add a tab for observability into your Reverse ETL syncs in the upcoming release. Stay tuned!

See our Health Dashboard documentation for more information on this feature.

Releases: Tracking Plan Observability Enhancements

Thu, 06 Jul 2023 00:00:00 +0000

We have introduced new observability features that increase your visibility and insights into tracking plan violations to help you maintain high-quality data.

With this update, you can directly track all tracking plan violations, their types, and sample violation events in the RudderStack dashboard. You can also monitor violations across different tracking plan versions within the previous 30 days.

To access the tracking plan violations, go to the Events tab of your source and click Violations under Event Details. Here, you can view the number of validated events, their type, name, events that violate tracking plan rules, and dropped events.

Violation types

RudderStack defines five violation types:

Additional-Properties
Required-Missing
Datatype-Mismatch
Unplanned-Event
Unknown-Violation

Note that each event can have multiple violations. See Violation types in our tracking plans documentation to learn more.

Violation counts

RudderStack also provides the violation count for each violation type. For example, if a single event violates a property missing rule, the count captures multiple missing properties associated with that violation. See Event details for more information.

Releases: Transformation Observability

Thu, 15 Jun 2023 00:00:00 +0000

We have updated our Transformations feature, focusing on improved visibility of transformation errors and provide an option to enable notifications.

Prior to this update, transformation errors were visible only under the Events tab of the destination. Based on your feedback, we have now introduced a dedicated Transformation Events option that provides a centralized view of transformation errors, enabling you to identify and take action on any issues quickly. With this option, you can easily filter errors across all destinations or focus on errors specific to a single destination. Additionally, you can now drill down into the errors and examine sample events, facilitating efficient debugging of transformation processes.

To further enhance your Transformations experience, we have also introduced a new notification feature for transformation errors. You can now enable notifications for transformation errors by navigating to the Settings tab. Once enabled, you will receive email notifications in case of transformation errors. Like other notifications, you will receive a maximum of one daily notification for each destination with a transformation error.

For more information on these updates, see Manage transformations.