AppSignal vs Server Density: What are the differences?
AppSignal: Monitoring for Ruby and Elixir. By developers, for developers. AppSignal gives you and your team alerts and detailed metrics about your Ruby or Elixir application Sensible pricing, no aggressive sales & support by developers.; Server Density: Trusted monitoring built by experts. SaaS-based scalable infrastructure monitoring to help businesses save time and money. With advanced server and website monitoring alerts, graphing tools and integrations with all major cloud service providers.
AppSignal and Server Density can be categorized as "Performance Monitoring" tools.
Some of the features offered by AppSignal are:
- Track errors
- Performance Monitoring
- Compare deploys. Monitor background jobs.
On the other hand, Server Density provides the following key features:
- Open source agent, plugin library, full API and Nagios compatibility
- Automatic install via script, system packages, Puppet, Chef, Ansible & Salt Stack
- Apps for iOS, Android, Apple TV and Slackbot
What is AppSignal?
What is Server Density?
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 AppSignal?
What are the cons of using Server Density?
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
Regarding Continuous Integration - we've started with something very easy to set up - CircleCI , but with time we're adding more & more complex pipelines - we use Jenkins to configure & run those. It's much more effort, but at some point we had to pay for the flexibility we expected. Our source code version control is Git (which probably doesn't require a rationale these days) and we keep repos in GitHub - since the very beginning & we never considered moving out. Our primary monitoring these days is in New Relic (Ruby & SPA apps) and AppSignal (Elixir apps) - we're considering unifying it in New Relic , but this will require some improvements in Elixir app observability. For error reporting we use Sentry (a very popular choice in this class) & we collect our distributed logs using Logentries (to avoid semi-manual handling here).