Tesla Performance Monitoring
HTTP client performance tracing for Tesla in your Elixir and Phoenix applications. Scout's Elixir agent instruments Tesla requests via telemetry automatically. See every external HTTP call in context alongside your Ecto queries, Phoenix request traces, and Oban job executions.
Errors, Logs, and Traces
Tesla HTTP Calls in the Context of Every Transaction
Scout captures Tesla HTTP requests as spans within the enclosing Phoenix controller, LiveView callback, or Oban job transaction. When a Tesla request is slow or fails, you see it alongside the Ecto queries and application code that surrounded it in the same trace.
Error Monitoring
HTTP errors from Tesla requests are captured within the transaction trace. Timeouts, connection failures, and unexpected status codes appear in context with the full trace.
Log Management
Log output is enriched with trace context. Filter logs by trace ID to see the full sequence of Tesla calls made during a specific Phoenix request or Oban job execution.
App Traces
Every Tesla HTTP request appears as a span in the transaction trace with URL, method, status, and timing. Slow external calls are surfaced so you can see their impact on overall request performance.
Query Analysis
External HTTP Performance Alongside Ecto Query Data
Scout shows Tesla HTTP call timing alongside Ecto query timing in the same transaction trace. This lets you see whether slow responses are coming from your database, your external service calls, or your application code.
Auto-Instrumentation
Telemetry-Based Tesla Instrumentation
Scout's Elixir agent 2.0 instruments Tesla via telemetry. Request start, stop, and exception events are captured automatically without adding middleware to your Tesla client modules.
Supported Frameworks
Works with the Tesla frameworks you already use
Scout auto-instruments the frameworks and libraries in your stack. No manual configuration required.
HTTP Clients
- Tesla
- Finch
- Req
Web Framework
- Phoenix
- Phoenix LiveView
- Plug
Background Jobs
- Oban
Database
- Ecto
Memory Profiling
Memory Bloat Detection for Tesla
External HTTP calls that return large response bodies can contribute to memory growth in Phoenix processes. Scout detects memory bloat at the transaction level, showing which requests are responsible for memory increases.
AI Native
Query Your Tesla App Data from AI Assistants and the Terminal
Scout offers hosted and local MCP servers with 17 tools, a Go CLI via Homebrew with TOON format, and a public API. Query your Phoenix application's external call performance alongside error and trace data from Claude Code, Cursor, or the terminal.
MCP Server
Hosted or local MCP server with 17 tools covering apps, endpoints, traces, errors, insights, background jobs, and usage data. Works with Claude Code, Cursor, VS Code Copilot, and any MCP-enabled assistant.
Scout CLI
Go binary available via Homebrew. Query app metrics, endpoint performance, traces, error groups, and insights from the terminal. Outputs human-friendly tables or TOON format for LLM consumption.
Public API
Full programmatic access to your monitoring data for building custom integrations, dashboards, or automation workflows.
Get Started in Minutes
Add Scout to Your Tesla App
Get Scout running on your Elixir app in under 3 minutes.
Add to your mix.exs:
{:scout_apm, "~> 2.0"}Download your customized config to config/scout_apm.exs.
Add instrumentation to lib/your_app_web.ex and deploy.
FAQ
Tesla Monitoring FAQ
Does Scout instrument Tesla HTTP calls?
Yes. Scout's Elixir agent 2.0 instruments Tesla via telemetry. Every Tesla request appears as a span in the enclosing transaction trace with URL, method, status, and timing. No Tesla middleware changes required.
How do I see Tesla performance in the context of Phoenix requests?
Scout captures Tesla requests as spans within the Phoenix controller or LiveView transaction trace. The Tesla call appears alongside Ecto queries and application code in the same trace timeline.
Does Scout support Finch and Req as well as Tesla?
Yes. Scout auto-instruments Tesla, Finch, and Req HTTP clients. All three appear as spans within the enclosing transaction trace with the same level of detail.
Does Scout capture Tesla errors?
Yes. HTTP errors from Tesla requests, including timeouts and connection failures, are captured within the transaction trace and linked to the surrounding context.