What to expect
Three things to keep in mind about Labs features.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. The stage 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 beta: We’re rolling these out gradually as we polish the rough edges. Some beta features sit behind a feature flag and may need to be enabled by Support. Share what you run into in our Discord channel.
- In preview: Closer to general availability. Self-serve and ready to try: turn it on yourself, explore what’s there, and share your feedback in our Discord channel.
Current Labs features
Apdex
In previewMeasure 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 anomaly detection triggers. Display them as a single value or time series, so you can see your current score at a glance.Read the Apdex docs →Share feedback on Discord →Log-based metrics
In previewTurn 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 (for example 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 log-based metrics docs →Share feedback on Discord →Set up with AI
In previewSet up AppSignal in your application with an AI agent and send your first data. In your organization, select Add app and then Set up with AI, then paste the prompt into your agent. The prompt includes a provisioning token and points to AppSignal’s agent instructions, so the agent can inspect your project, choose the right integration, and confirm details such as application name and environment before it changes files. Setup is complete when your first data reaches AppSignal.This works with agents that can read a URL and edit files, such as Claude Code, Cursor, or Codex.Read the AI setup docs →Browse the agent instruction files →Share feedback on Discord →
Distributed tracing
In previewFollow a request as it travels across your services and applications. Distributed tracing is built on OpenTelemetry. Its trace timeline shows every span in a request, across service boundaries, so you can see where the time goes. When a trace crosses more than one service, a service map shows which services it reached and how long each call took. The service map is now available to everyone.Available for Python, Ruby, and PHP, and for any OpenTelemetry-instrumented application that reports to a hosted collector. We’d like to hear what works and what you’d want from it next.Read the distributed tracing docs →Set up distributed tracing →Read the trace page docs →Share feedback on Discord →
AppSignal CLI
In betaA command-line interface for AppSignal, built in Rust. Designed for both people and AI agents to query your AppSignal data from the terminal. Install it with Homebrew.We’ll keep expanding the CLI toward feature parity with the AppSignal API.Read the AppSignal CLI docs →Install the CLI →See the latest releases →
Browser monitoring: front-end errors and Core Web Vitals
In betaFront-end monitoring for your browser apps, in its own Browser section. Front-end errors arrive with a breadcrumb trail of what the user did before them, collected without configuration. Core Web Vitals from real users (LCP, INP, CLS, FCP, and TTFB) are aggregated per route, so you can see which are slow and filter by app version to compare releases. Collection is handled by
@appsignal/browser, a new standalone package that replaces @appsignal/javascript.Read the browser monitoring docs →Install @appsignal/browser →Share feedback on Discord →New Slack app
In betaSlack app is a newly rearchitected Slack integration with two-way sync. Supports actions to close, reopen incidents or change an assignee. Closing an incident in AppSignal UI will be reflected on the corresponding Slack notification.Add Slack from Add new notifier on the Notifications page.Read the Slack integration docs →Share feedback on Discord →
Responsive UI for mobile
In betaWe’re improving the responsive UI for mobile users, so you can read and act on your data from a phone. So far this covers:
- Dashboards and the Discover AppSignal page
- The Logs page filters
- App and organization settings
- The time and date filter, and Time Detective
- Page titles and breadcrumbs
- Error breadcrumbs
- The trace timeline
GitHub bidirectional sync
In betaToday, Send to GitHub creates a GitHub issue from an incident. We’re rebuilding the integration so changes in GitHub update the incident too.Already available:
- An incident can link to more than one issue or pull request. Mention one in a note, and AppSignal links it.
- Paste an incident’s URL in the description of a GitHub issue or pull request, and AppSignal links it to the incident.
- Each linked issue shows whether it is open, closed, or merged. AppSignal updates the status when it changes on GitHub.
- Status changes show in the incident’s logbook, with who made them on GitHub.
- Assignees match in AppSignal and GitHub
- An incident reopens when its GitHub issue reopens
- An incident closes when its linked pull request is merged and deployed
- GitHub issue comments show on the incident
- AppSignal adds labels to new issues based on the incident type
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
Will Labs features affect my production data?
Will Labs features affect my production data?
No. Labs features operate alongside your existing setup with explicit opt-in where needed.
Can I disable a Labs feature?
Can I disable a Labs feature?
Yes, at any time. Your configuration is preserved.
What happens to my feedback?
What happens to my feedback?
The team building that feature reads every piece of feedback.