Skip to main content

​
What to expect

Three things to keep in mind before you opt in.

Early access

Use features before they’re generally available.

Rough edges

Features may be incomplete or change without notice. Not covered by our SLA.

Direct influence

Your feedback goes straight to the team building the feature.

​
Stages

Each Labs feature sits at one of three stages, which tells you how to get involved:
  • In research: We’re exploring the problem and shaping the solution. You may see early pull requests, prototypes, or open calls for UX research sessions. Join a session to help us scope what we build.
  • In preview: Self-serve and ready to try. Turn it on yourself, explore what’s there, and share your feedback in our Discord channel.
  • In beta: Closer to general availability. Some beta features sit behind a feature flag and may need to be enabled by Support. We’re rolling these out gradually as we polish the rough edges.

​
Current Labs features

Apdex

In betaMeasure how satisfied your users are with your application’s performance. Set Satisfied and Tolerating response time thresholds per namespace, and AppSignal generates apdex and apdex_counts metrics you can add to dashboards and notifications. Display them as a single value or time series, so you can see your current score at a glance.Share feedback on Discord →

Log-based metrics

In betaTurn data from your logs into metrics without writing any new code or leaving the Logs page. Filter your logs to the events you care about, like requests to /api/orders, select Create a metric from a log line, and AppSignal builds a Count, Gauge, or Measurement metric using the query, severity, and source you already had open. Use it on a dashboard or in a trigger.Read the doc →Share feedback on Discord →

AppSignal CLI

In previewA command-line interface for AppSignal, built in Rust. Designed for both humans and LLMs to query your AppSignal data from the terminal. Install it with Homebrew to get started.Install the CLI →See the latest releases →

JavaScript web vitals

In researchFrontend monitoring for your browser apps. We’re exploring a browser section that surfaces frontend errors along with the context of what happened before them, plus Core Web Vitals from real users, broken down per page. Track the standard browser metrics, LCP, INP, CLS, FCP, and TTFB, to see how each page performs. Filter by app version to compare the performance of each release. Useful for developers debugging slow pages and for analytics.Join the research →

Distributed tracing

In researchFollow a request as it travels across your services and applications. We’re exploring distributed tracing built on OpenTelemetry, with a trace timeline that shows every span in a request, even when it crosses service boundaries, so you can see where the time goes and where one service hands off to another. A service map surfaces the upstream and downstream callers around a trace, answering who you depend on and who depends on you. Handy for debugging slow requests and understanding how your services fit together.We’re now looking for people to try out the early UI and tell us what works and what they’d want from it. If you’d like to help shape where this goes, we’d love to hear from you.Join the research →

​
Get involved

UX research sessions

30-minute video calls where you share what’s working and what isn’t.

Feedback

Use the in-feature feedback button or join us on Discord.

​
FAQ

No. Labs features operate alongside your existing setup with explicit opt-in where needed.
Yes, at any time. Your configuration is preserved.
The team building that feature reads every piece.