The past month brought a lot of new surface area. Elixir support expanded significantly, the Scout CLI is now available, and new capabilities landed across the public API and MCP server.
Most of this work is focused on one thing: making Scout’s data accessible and actionable wherever you work, whether that’s the UI, your terminal, or an AI coding session.
Elixir Support
The Elixir agent now includes error monitoring and log management alongside performance tracing. When an exception fires you get the error, the request trace, and the surrounding log context in one view.
Error capture is telemetry-driven. The agent attaches to Phoenix and LiveView error events automatically, no changes to your controllers or LiveView modules required. Log output is enriched with trace context and forwarded alongside performance data.
LiveView instrumentation covers mount, handle_event, and handle_params with timing for each phase. Finch and Tesla HTTP clients are auto-instrumented, as is Oban for background job visibility. External service calls now appear in a dedicated section with per-service latency and query counts.
Released in Elixir agent 2.0
Scout Outside The UI
Public API - New endpoints for usage data by endpoint and time range, background job performance by class, and individual job execution records.
OpenAPI Spec - Now published and linked from your account settings. These are the same endpoints backing the CLI and MCP server, now available for building against directly.
MCP Server - Now includes background job performance alongside endpoint and database insights. A remote OAuth-based variant is also available for teams that prefer not to run Docker locally.
Scout CLI - Now available via Homebrew. It covers the main things you’d otherwise open the UI for such as querying insights, pulling traces by endpoint or job, and browsing API usage. The output format pipes cleanly into language models, making it useful alongside AI coding assistants.
Platform and Security
AWS Marketplace support is fully live. Scout subscriptions are available there for organizations that route software procurement through AWS.
2FA has moved from Authy to a native TOTP implementation. Any standard authenticator app works. If you have Authy-based 2FA configured, you’ll be prompted to migrate on your next login.
From the Scout Community
Monitoring Phoenix LiveView Performance With Scout: LiveView doesn’t behave like traditional endpoints. We break down how Scout instruments mount and event handlers and how to avoid flooding traces with high-frequency events. → Read more
How a singleton pattern broke our Django logging: A bug caused Scout’s logging handler to initialize seven times before settings loaded. The fix: defer initialization and share a singleton provider. → Read more
Give our new features a spin, and let us know what you find useful, we’re curious.