Summary

Hud now surfaces forensic samples directly on endpoint and queue pages, helping you move from high-level signals to concrete evidence with fewer clicks.

Details

A new "Forensics in this flow" table appears on all endpoint and queue pages. It lists sampled runs captured when Hud detects unusual behavior, including failures and duration-based triggers such as Exceeded Duration. Each entry shows detection time, trigger type, and run duration, making it easy to spot patterns. Selecting a row opens the full forensic view for that specific run.

Why It Matters

You can quickly validate anomalies, inspect real execution data, and get to root causes faster without navigating away from the flow you're investigating.

How to Access

Open any endpoint or queue in the Hud Web App and scroll to the Forensics section to review recent samples.

Summary

Hud now detects new or sharply increased errors immediately after each deployment, helping you validate stability and identify regressions within minutes.

Details

This update adds automatic detection of sudden error spikes following a deploy. Hud correlates each issue to the deployed version, highlights likely root-cause functions, and distinguishes between new errors and increased existing ones across endpoints and queues. Alerts are delivered across Web, Slack, and MCP, all with deploy time context.

Why It Matters

This closes the loop between deployment and detection. You can immediately see whether a release introduced failures and understand where they originated.

How to Access

Deploy your latest version and Hud will automatically monitor affected endpoints and queues.

Post-deploy alerts require Node SDK v1.6.28+ or Python SDK v0.3.20+.

Summary

Hud now captures and analyzes GraphQL operations with the same visibility and workflows available for REST, so teams using GQL get full monitoring parity across the Hud Web App and MCP.

Details

Hud automatically tracks GraphQL operations and displays them in the Endpoints list and MCP tools. Each operation is identified by its operation name, and the method reflects the operation type (query, mutation, subscription). Metrics, trends, flows, and alerts all work the same way as they do for REST endpoints. Errors are detected from response bodies and failure messages to ensure accurate issue tracking.

Why It Matters

Teams using GraphQL can monitor performance, errors, and regressions with the same depth and reliability they expect from Hud's REST support.

How to Access

Update to Node SDK version 1.6.36+ and send a few GraphQL requests. Your operations will appear automatically in the Hud Web App and MCP.

Summary

Hud now adds P99 and P50 duration metrics across Web graphs and MCP, giving teams clearer visibility into both typical behavior and extreme slowdowns.

Details

Duration charts now include P99 and P50 in addition to Avg and P90. These metrics are available across Issues, Endpoints, Queues, and Functions. The default view remains Avg and P90, and you can toggle P50 and P99 when deeper analysis is needed. This helps distinguish rare outliers from meaningful performance regressions.

Why It Matters

You get a more complete view of real production performance, allowing you to prioritize issues that impact users and improve reliability with confidence.

How to Access

Open any performance graph in the Hud Web App to toggle P50 and P99, or ask your agent to display these metrics in Hud MCP.

Summary

Hud's new Issues mechanism groups related events into persistent, lifecycle-tracked issues, giving teams clearer context, fewer alerts, and a more accurate view of what is happening in production.

Details

Hud now assigns stable IDs to issues, allowing each problem to be tracked from first detection through resolution. Related errors - such as HTTP 500s caused by the same underlying exception - are grouped into a single issue instead of separate alerts. The new Issues Dashboard brings these signals together across services, with filters and forensic data to help teams investigate faster. Auto-labels highlight first-time issues, spikes in error rates, and regressions tied to recent deployments. Slack alerts now fire once per issue, reducing noise while preserving visibility.

Why It Matters

By consolidating related errors into a single, persistent issue, teams gain a clearer picture of root causes, reduce alert fatigue, and accelerate time to resolution.

How to Access

Use the Issues Dashboard in Hud Web to explore and manage active issues. New grouping and alerting behavior is available immediately for projects running Node SDK v1.6.28+ or Python SDK v0.3.20+.

Summary

Hud now identifies sustained performance regressions with higher accuracy, reducing noise and highlighting slowdowns that truly matter.

Details

The updated degradation detection system analyzes hourly P90 averages with added consistency checks to avoid false positives. Alerts trigger only when regressions persist over time or when a new slowdown clearly emerges on your charts. Detection now applies to both endpoint and queue rules and compares performance day-over-day and week-over-week.

Visual improvements such as better contrast and smoothing make slowdowns easier to see and track.

Why It Matters

You get fewer noisy alerts and more reliable signals about real performance issues, helping you respond quickly and with confidence.

How to Access

Improved degradation detection is enabled by default for new alerts. To adjust thresholds or behavior, open the Rules page in Hud.

Hud now monitors both Kafka and SQS queues for errors and performance regressions, so you can catch issues earlier and keep your systems healthy.

What’s New?

• Extended all degradation rules (1d, 1w) to SQS queues
• New Queue Errors rule (SQS): detects message processing errors and points to the failing function
• New Queue Post-Deploy Degradation rule: alerts when a deployment slows down queue processing
• Forensics included in alerts to help you understand and fix issues fast

Queue rules are enabled by default, so you can benefit from them right away and catch errors and degradations as soon as they happen. You can fit rule thresholds to your needs on the Rules page.

You can now connect Slack to Hud and configure exactly where each service’s Issues appear.

After installing Hud’s Slack app and adding it to your channels, you can set up routing rules so each service’s Issues go to a dedicated Slack channel. This gives your team more control, keeps alerts relevant, and avoids noise in shared channels.

Head to your Slack settings in Hud to get started.

For more information on how to set it up, read our guide.

You can now see all Issues related to a specific endpoint directly from the Endpoint page. This provides better context and helps you troubleshoot faster - no need to filter through the general Issues page.

What’s included:

• A dedicated table showing all Issues related to the selected endpoint
• Red dot indicators on the Behavior Graph whenever an Issue with Forensics is detected

This update makes it easier to stay focused on the endpoints you care about while investigating performance or reliability issues.

We’ve launched a brand new Overview page to help you monitor and understand your services faster than ever.

What’s New

• High-level mapping summary: Instantly see how many endpoints, queues, and functions are mapped across your environment.
• Fixing Opportunities: Prioritized view of failing components with quick actions to create alerts or start an MCP investigation.
• Performance Insights:
  • Slowest Components: Identify which endpoints or functions are taking the longest.
  • Highest Error Rates: Spot stability issues with trending error data.
  • Most Invoked: See what’s running most frequently in your stack.

Why It Matters
Whether you're debugging issues, tracking changes, or just trying to stay on top of your system's behavior - the Overview page gives you a unified starting point with actionable insights.

Available now for all environments. Go to Overview from the sidebar to explore.