AppSignal vs Blackfire.io: 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.; Blackfire.io: Blackfire Profiler automatically instruments your code to gather data about consumed server resources like memory, CPU time, and I/O. Blackfire achieves a new level of accuracy by aggregating several profile samples and getting rid of non relevant data. Get even deeper and review the interactions with your entire stack (SQL database engines, cache servers, ...).
AppSignal and Blackfire.io 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, Blackfire.io provides the following key features:
- Profile a page at a mouse click thanks to the Blackfire web browser extension
- Browse through the function calls and identify performance bottlenecks thanks to the Blackfire intuitive UI
- Because Blackfire is only triggered when you profile a request, there is no overhead for other requests
"Easy setup" is the primary reason why developers consider AppSignal over the competitors, whereas "Deep insights into PHP request cycle" was stated as the key factor in picking Blackfire.io.
Publitas, Tolq, and inkl are some of the popular companies that use AppSignal, whereas Blackfire.io is used by Blackfire.io, Showpad, and Basharsoft. AppSignal has a broader approval, being mentioned in 24 company stacks & 5 developers stacks; compared to Blackfire.io, which is listed in 7 company stacks and 4 developer stacks.
What is AppSignal?
What is Blackfire.io?
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 Blackfire.io?
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).