SLO issues now have a configurable threshold, a duration graph showing the breach, and correlated forensics on the issue page.

What's New?

• P100 detection — SLO breaches are now detected on P100 (worst-case latency), catching every request that exceeds your threshold.
• Configurable SLO duration — Set the SLO threshold for any endpoint or queue directly from the rule page.
• Duration graph on the issue page — See the breach visualized with the SLO threshold drawn as a line.
• Correlated duration forensics — The issue page shows forensic samples that match the entity, exceed the SLO duration, and fall within the breach window.

Why it matters SLO issues previously lacked a graph, matching forensics, and an easy way to adjust the threshold. Now the full investigation loop, from detection to evidence, lives on one page.

Try it out Open an existing SLO issue in the Issues page to see the new graph and forensics, or go to any SLO rule to configure the threshold.

Control how capacity is allocated across your services, directly from the web app.

What's New

• A new Account Usage page in Settings showing total session capacity, per-service usage, limits, and usage percentages
• Admins can adjust the session limit for any service. Protect critical services with more room, or cap high-growth services so other teams aren't squeezed out
• Configure the default session limit that applies to every new service automatically

Why It Matters Scale Hud across more teams with confidence. Set per-service limits so no single service monopolizes your account's capacity, and rebalance allocation as priorities shift. Onboard new teams without disrupting what's already running.

How to Use Go to Settings > Account Usage to view your per-service breakdown and start adjusting limits. Only account admins can change service limits. To grant admin access to a teammate, contact support and we'll be happy to assist.

Every issue in Hud now has a ready-made prompt you can copy into your AI coding agent, turning any issue page into a direct launch point for agentic investigation and remediation.

What's New

• Prompt to Fix for all issue types — Each issue type gets a dedicated prompt that identifies the problem and tells the agent exactly which Hud MCP tools to call.
• Powered by Hud MCP — Prompts are now based on MCP rather than embedding context inline. This means your agent gets access to the full depth of Hud's production data during investigation. The result is richer, more accurate investigations with real production context.
• Open in Cursor — If you're using Cursor with Hud MCP installed, an "Open in Cursor" button sends the prompt straight to your agent.

Why It Matters Before, only error issues had a guided path from Hud into your coding agent, with a large but partial inline context. Now, every issue page is a one-click bridge to agentic investigation, backed by the full production context Hud provides through MCP.

How to Use Open any issue and click "Prompt to Fix" to get a ready-made prompt for your AI coding agent. For best results, install Hud MCP if you haven't already.

Hide, show, and reorder columns across all entity tables to focus on the data that matters to your investigation.

What's New

• Drag to reorder - Move columns into the order that fits your workflow. Your layout is saved.
• Hide/show columns - Remove columns you don't need, bring them back when you do.
• Works across all tables - Endpoints, Functions, Queues, and Services pages all support column customization.

Why It Matters Tables with many metrics can get wide. Instead of scrolling back and forth to compare a function name with its duration, put the columns you care about side by side. When you need to screenshot findings for your team, the view is already clean.

How to Use Open any entity table and look for the column settings control to start customizing your view.

You can now see which real production forensic samples a function participates in, even when it is not the root cause.

Details

A new Forensics table is available on the Function page. It lists all forensic samples where the function appears anywhere in the execution flow, not just as the root. The table behaves exactly like the existing Endpoint and Queue forensics tables, including sorting, filtering, and navigation.

Why It Matters

Function-level investigations no longer stop at errors and metrics. Instead of guessing which incidents a function might be involved in, you can now view concrete production samples and understand what actually happened.

How to Access

Open a function in Hud Web and scroll to the Related Forensics section to see the production forensic samples the function participated in.

You can now view P100 to understand the worst-case latency in your system. This helps surface rare but severe performance spikes that averages and lower percentiles can hide.

Details

• P100 added to duration graphs across endpoints, functions, queues, and issue pages.
• Improved percentile selector lets you adjust which percentiles are visible as you investigate. Your selection is saved.
• Custom Pxx selection allows choosing any percentile from 1 to 100 to match your debugging workflow.

Why It Matters

When users report intermittent slowness, P100 shows the true worst-case execution time. Comparing P100 with P50 or P95 helps you quickly determine whether the issue is a rare outlier or a broader performance degradation.

How to Access

Open any duration graph and add P100, or select custom percentiles using the distribution selector.

You can now save your preferred filters as defaults and use new exclusion filters to keep irrelevant data out of view. These updates help you start every session with a clear, focused workspace.

Details

• Persistent filters: Use "Save as Default" to store your current filter set as your personal default for each table.
• New "Not" filters: Exclude specific folders, files, or paths across Endpoints, Functions, Queues, and Services.

Why It Matters

These improvements reduce repetitive setup and help you concentrate on the endpoints, functions, and queues that are actually relevant to your investigation. You get a consistent, streamlined view every time you return to Hud.

How to Access

Open any table, set your filters, and select "Save as Default" to make them persistent across sessions.

Hud now includes a Total Duration metric across Functions, Endpoints, and Queues, making it easier to see which parts of your system consume the most cumulative time.

Why It Matters

Avg Duration shows slowness and Invocations show volume, but neither reflects true impact. Total Duration combines both, helping teams quickly identify the entities that account for the most total time and are the best candidates for optimization.

How to Access

Open any Functions, Endpoints, or Queues table in Hud Web and enable sorting on the Total Duration column.

You can now filter the entire flow by the session and timeframe of a forensic sample, making it easier to understand what happened during a specific performance outlier.

Details

Hud now includes a Filter by this forensic action on performance forensic samples. When applied, Hud automatically sets the global timeframe to the forensic window and filters the “Functions in this flow” table by the relevant session ID. Navigation is session-aware, so clicking into any function keeps the same session filter applied as you move through the flow.

Why It Matters

Performance regressions often impact only a single session. Filtering the app to match the exact session and timeframe of the outlier removes noise and helps teams focus on the precise operations that caused the slowdown.

How to Access

Open any Performance Forensics sample and select Filter by this forensic. The flow and functions data will immediately update to reflect that specific session.

You can now turn any duration outlier sample into a ready-to-use investigation prompt for your code agent, helping you move from evidence to action faster.

Details

The Forensics table now includes a new “Prompt to Fix” option for duration outlier samples. Each prompt is prebuilt to describe the issue and provide a clear task for your agent. When used with Hud MCP, the prompt includes the runtime context needed for the agent to investigate the root cause and propose a fix. This feature currently supports forensic samples captured as duration outliers.

Why It Matters

Duration outliers often signal hidden performance problems. Having an actionable prompt lets you immediately investigate with full context instead of starting from scratch.

How to Access

Open any endpoint or queue in Hud Web, scroll to the Forensics table, select a duration-based sample, and click “Get Prompt to Fix”. Paste the generated prompt into Cursor with Hud MCP enabled.

Feature requires the “Duration Forensics” capability enabled by the customer operations team.