Consul vs New Relic

• Key-Value database management.
• Service discovery.
• Centralized configuration database with native high availability.

Read full review

• Monitor traffic rates and server usage on real time
• Helps engineers to dive deep into an issue and guides them to the root cause
• Provides high-level system health status of different components (ie. Server capacity, RPM, page load time, error rate..)
• Near real time reporting
• Links with deployment so easy to understand if an issue has occurred after a particular release

Read full review

• The GUI: The GUI interface for Consul has gotten a lot better over the years. Since Consul is so easy to interact with via API, this isn't a showstopper, but for those that are less command line inclined it's always nice to be able to refer them to an easy to use and understand web interface
• It's chatty: Consul is extremely chatty. Sometimes it's particularly chatty at 2am with no indication as to why and eats up quite a bit of resources. Just be sure to provision your systems that typically take a heavy load with a little extra for Consul

Read full review

• It would be helpful if use cases for particularly a Windows installation, were provided to help determine which set of configuration files would be the one a group would want to control. I.e. potentially with a department trying to do DevOps, it's difficult to determine which team needs to have responsibility for what at times. The reason I mention this, is New Relic seems to in many ways be a tool that's useful for DevOps-related processes and staff.
• On the main New Relic One site, sometimes a refresh option is available for new features. It would be helpful to see what the new features are in advance before trying this out. Particularly if doing a demo or a working season with another team.
• I'm not aware of a page or specific site which describes/summarizes all of the different NR Products and their features.
• Sometimes it's tricky to determine which product to use to accomplish a task.

Read full review

• It contains a native web UI, which in contrast to its counterparts, is handy, very intuitive and - most importantly - very informative. It leaves no room for doubt about your services "forest" health. So, for that purpose, the learning curve was almost down to non-existent. Our team managed to work seamlessly with Consul being our services API
• Our management staff had a difficult time understanding what Consul was really all about. For technical staff it is pretty simple to understand the huge value such a tool can pose to our suite of solutions, but once our management staff took the grasp of its valuable handy set of tools, we didn't take long to start using it and keeping track of our Swarm overall health, with was a constant concern for the entire company before.
• For load balancing purposes, we were relying pretty much on guesses before we decided to use Consul. One would check a certain node overall health and decide if we would need to spring a new instance at AWS or Digital Ocean.

Read full review

• Gives us great visibility into what our services are doing at all times.
• Alerts us quickly when there is a problem so we can address it with alacrity.
• Gives us extremely customizable options in regards to how we want to track, store, and materialize our data.

Read full review