How is error volume calculated for billing?
Error volume above the included limits is billed in arrears as "on-demand" usage at $5 per additional 50,000 events.
Stop chasing errors across multiple tools – Scout's Error Monitoring captures exceptions with full context right alongside your performance data! Our Error Monitoring solution streamlines debugging by integrating error tracking and APM data into a single, intuitive interface.
Stop juggling multiple tools and let Scout bring your errors and performance data together! Intelligent grouping and automatic context capture give you exactly the error data you need, when you need it, with integrated insights on your performance metrics. Even more conveniently, complete integration with Scout Monitoring.
Automatically collect request parameters, session data, and custom context to get the full picture of what was happening when the error occurred.
Smart grouping prevents error spam and focuses on unique issues, organizing by stack trace similarity and occurrence location.
Instant notifications when new errors occur or existing ones spike, with flexible rules based on severity and frequency.
Assign errors to team members, set status, and manage notification preferences for better organization and accountability.
Find exactly what you need, when you need it. Our intelligent error detection and filtering approach lets you efficiently manage thousands of errors without getting overwhelmed, with the specific features you need:
Tag critical endpoints to prioritize errors automatically
Fix fast with stack traces and GitHub integration for deeper info
Instantly locate and filter errors by specific controller actions and endpoints for focused debugging
Narrow your search parameters before loading data to efficiently explore large error volumes
Filter loaded errors in real-time using powerful search patterns to find exact matches
Monitor error trends with clear indicators showing error frequency and impact over time
Scout keeps your error data organized and accessible! Understand your application's error patterns with real-time error tracking and trend analysis. Monitor both error frequency and resolution rates to optimize your debugging strategy and stay on top of application health. All error data is retained for 30 days, with flexible severity level filtering to help you focus on what matters.
Straightforward and transparent pricing means you can worry about your application, not your bill.
Start with our free tier during the beta and reach out to support@scoutapm.com if you need more data.
With monitoring that "just works" for Rails, Django and more, get running in minutes with Scout's streamlined setup. No extra code needed - just deploy our agent and start getting insights in 5 minutes.
Get started in under 3 minutes with our easy to install Ruby agent.
Install our gem. In your gemfile:
gem 'scout_apm'
Shell:
bundle install
Download your customized config file, placing it at config/scout_apm.yml
.
Deploy.
We initially provision your application using environment variables instead of the config/scout_apm.yml
. Configuration values set via env variables will take priority over those set via yaml.
For Django, use the following steps (Flask and friends, see full docs):
Install the scout-apm
package:
pip install scout-apm
Configure Scout in your settings.py
file:
# settings.py
INSTALLED_APPS = [
"scout_apm.django", # should be listed first
# ... other apps ...
]
# Scout settings
SCOUT_MONITOR = True
SCOUT_KEY = "[AVAILABLE IN THE SCOUT UI]"
SCOUT_NAME = "A FRIENDLY NAME FOR YOUR APP"
If you wish to configure Scout via environment variables, use SCOUT_MONITOR
, SCOUT_NAME
, and SCOUT_KEY
instead of providing these settings in settings.py
.
Deploy.
It takes approximately five minutes for your data to first appear within the Scout UI.
If you've installed Scout via the Heroku Addon, the provisioning process automatically sets SCOUT_MONITOR and SCOUT_KEY via config vars. Only SCOUT_NAME is additionally required.
Scout supports Laravel 5.5+.
Not using Laravel? Check our documentation.
Install the scoutapp/scout-apm-laravel
package:
composer require scoutapp/scout-apm-laravel
Install the scoutapm
php extension (optional, recommended):
sudo pecl install scoutapm
Configure Scout in your .env
file:
# Scout settings
SCOUT_MONITOR=true
SCOUT_KEY="[AVAILABLE IN THE SCOUT UI]"
SCOUT_NAME="A FRIENDLY NAME FOR YOUR APP"
Add the config/scout_apm.php:
php artisan vendor:publish --provider="Scoutapm\Laravel\Providers\ScoutApmServiceProvider"
Clear and re-cache your config:
php artisan config:cache
Deploy.
It takes approximatively five minutes for your data to first appear within the Scout UI.
If you’ve installed Scout via the Heroku Addon, the provisioning process automatically sets SCOUT_MONITOR
and SCOUT_KEY
via config vars. Only SCOUT_NAME
is required.
For a Phoenix app, add our package to mix.exs
(and run mix deps.get
):
{:scout_apm, "~> 1.0"}]
Download your customized config after signing up and place at config/scout_apm.exs
Add to your app:
# lib/your_app_web.ex
defmodule YourApp.Web do
def controller do
quote do
use Phoenix.Controller
use ScoutApm.Instrumentation
...
See our full installation guide to get the most out of your Scout instrumentation!
Error volume above the included limits is billed in arrears as "on-demand" usage at $5 per additional 50,000 events.
Our Error Monitoring packages depend on the base Scout agent, so this is not entirely possible. That said, you can easily sign up for a free Scout account and configure Error Monitoring from there!
Our Error Monitoring is currently available for Ruby and Python.
Yes! Scout makes it very easy to filter errors by severity level, error type, or custom attributes. You can also set up ignore rules for known issues.
Join engineering teams who trust Scout Monitoring for hassle-free performance monitoring. With our 3-step setup, powerful tooling, and responsive support, you can quickly identify and fix performance issues before they impact your users.