Nagios vs OpenTracing: What are the differences?
Nagios: Complete monitoring and alerting for servers, switches, applications, and services. Nagios is a host/service/network monitoring program written in C and released under the GNU General Public License; OpenTracing: Consistent, expressive, vendor-neutral APIs for distributed tracing and context propagation. Consistent, expressive, vendor-neutral APIs for distributed tracing and context propagation.
Nagios and OpenTracing belong to "Monitoring Tools" category of the tech stack.
Nagios and OpenTracing are both open source tools. It seems that OpenTracing with 1.82K GitHub stars and 175 forks on GitHub has more adoption than Nagios with 60 GitHub stars and 36 GitHub forks.
According to the StackShare community, Nagios has a broader approval, being mentioned in 177 company stacks & 40 developers stacks; compared to OpenTracing, which is listed in 8 company stacks and 11 developer stacks.
What is Nagios?
What is OpenTracing?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose OpenTracing?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Nagios?
What are the cons of using OpenTracing?
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 use Nagios to monitor our stack and alert us when problems arise. Nagios allows us to monitor every aspect of each of our servers such as running processes, CPU usage, disk usage, and more. This means that as soon as problems arise, we can detect them and call out an engineer to resolve the issues as soon as possible.
We use Nagios to monitor customer instances of Bridge and proactively alert us about issues like queue sizes, downed services, errors in logs, etc.
We use nagios based OpsView to monitor our server farm and keep everything running smoothly.