PagerDuty vs Scout: What are the differences?
Developers describe PagerDuty as "Incident management with powerful visibility, reliable alerting, and improved collaboration". PagerDuty is an alarm aggregation and dispatching service for system administrators and support teams. It collects alerts from your monitoring tools, gives you an overall view of all of your monitoring alarms, and alerts an on duty engineer if there's a problem. On the other hand, Scout is detailed as "Application Monitoring that Developers Love". Scout is application monitoring that points developers right to the source of problems: N+1 database queries, memory bloat, performance trends, and more Scout eliminates much of the investigation part when performance woes occur. .
PagerDuty belongs to "Monitoring Aggregation" category of the tech stack, while Scout can be primarily classified under "Performance Monitoring".
Some of the features offered by PagerDuty are:
- Alerting that works (and wakes you up)- When your systems go down, PagerDuty will wake you up. You choose how you want to be alerted - via phone, SMS or email, to multiple numbers, with retries.
- Integrate all your existing monitoring tools- PagerDuty works great with almost all monitoring tools including: Nagios (and Icinga), Keynote, New Relic, Pingdom, Circonus, Red Gate SQL Monitor, Server Density, Zenoss, Monit, Munin, SolarWinds and many others. If it can send email, it will work with PagerDuty.
- Native apps with push notifications- iOS and Android native apps with push notifications and a cross-platform mobile website ensure you can respond to alerts wherever you are, even on the go.
On the other hand, Scout provides the following key features:
- Monitors Ruby & Elixir apps with more languages to come
- Easy install
- Detailed transaction traces
"Just works" is the primary reason why developers consider PagerDuty over the competitors, whereas "Easy setup" was stated as the key factor in picking Scout.
According to the StackShare community, PagerDuty has a broader approval, being mentioned in 303 company stacks & 47 developers stacks; compared to Scout, which is listed in 29 company stacks and 7 developer stacks.
What is PagerDuty?
What is Scout?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Scout?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
We love Scout at Rollbar. Here's how we use it.
Zero configuration monitoring for new hosts
We have added Scout to our Ansible configuration for new host setup. So, when we provision a new machine, we get basic monitoring without any extra configuration. Once the host is up and running, we add it to the appropriate role in Scout and all of our monitoring plugins are magically deployed and enabled on the new host.
Monitoring HTTP response codes
One of the best things about Scout is how beautiful and therefore usable their graphs are. We have a Scout dashboard which shows all of our response codes which allows us to quickly see connections between different hosts when problems occur.
Scout's plugin model makes it really easy to extend. We have implemented our own log monitoring plugin which reports metrics like the 90th percentile of slow queries on our site. These types of plugins allow us to see issues at a glance during deploys, maintenance and load spikes.
Slowly taking over Nagios
Nagios is amazing, but let's be real... Anyone who has used it knows how painful it is to set up, administer and extend. We are in the process of cutting over from Nagios to Scout to handle more of our infrastructure monitoring and soon, alerting.
I'm a freelance developer with a handful of servers that needed insightful monitoring and alerts. I searched high and low across both hosted and self hosted solutions... paid and open source. While many are quite capable the self-hosted solutions were clunky and overkill. The few self-hosted for pay solutions costs structure were completely outside of a freelances budget. ScoutApp is the first that had the easy to use setup, amazing plugins for specific app monitoring and the price was actually affordable. Setup couldn't be easier. Plugins are handled amazingly with a single click that initiates the agent to install remotely. The interface is minimal and easy to read. Triggers are so well done and easy to setup with clear human language detailing the alert criteria. Real-time graphing is just icing on the cake.
ScoutApp is great for not just small but enterprise level infrastructures as well. Added features such as roles, multi-user accounts, environments and even an API make growing with it a no brainer.
Very well done and highly recommended.
I used to have NewRelic on https://doorbell.io for my monitoring. It worked pretty well for the basic things, and the basic plan is free.
However, as https://doorbell.io's stack got increasingly complicated, the plugins of NewRelic didn't work as well as I needed, in order to reliably monitor all aspects of the platform.
I decided to try out Scout as an alternative, since even though it doesn't have a free plan, the basic plan is only $8/month (compared to $149 for NewRelic).
I found the interface to be really good, and they have great documentation. I found plugins for every single part of my stack, and they all worked very easily "out of the box". And best of all, added practically no overhead to the server!
So overall, I'd say it's a service that's well worth paying for. It's a steal at $8/month!
We migrated our infrastructure monitoring to Scout about six months ago when our previous monitoring solution became unreliable and cumbersome to maintain. We were pleasantly surprised at the ease of implementation and the library of plugins already available.
The fine grain polling frequency and long term metric logging helped us maintain the high level of uptime our application requires. Moreover, due to the nature of the Scout protocol, changes to our specific application monitoring can be configured at a high level in their interface with a few clicks.
For the few times we have been in communication with their support team to help sort our questions or clarify details, we have been thoroughly impressed at their response time and personalized attention to our needs.
We highly recommend using Scout.
We are a very small non profit with a very simple server setup. Our two developers do not have any special training as sys admins. But it was very easy to get setup with Scout and start some simple monitoring of our servers. Most of what we do is check that some key processes are running and that our URLs are up. It was easy to do all of that with Scout. That said: we're interested in learning more about Scout's capabilities and doing more sophisticated server monitoring down the line.
Pagerduty integrates with pretty much everything, and for the ones it doesn't its easy to get it done!
We are a very small non profit with a very simple server setup. Our two developers do not have any special training as sys admins. That said, it was very simple to get setup with Scout and start some simple monitoring of our servers. Most of what we do is check that some key processes are running and that our URLs are up. But we're interested in learning more aboutS Scout's capabilities/ doing more sophisticated server monitoring down the line.
whistles If there's something weird, in your infrastructure, who you gonna call?
DevOps-Buste.. You get the idea. PagerDuty is great for quickly notifying us when things go pearshaped.
Luckily we don't end up actually using this much, but we couldn't live without it.
alerts me to any issues and blends well with other tools for uptime monitoring