Alternatives to Observium logo

Alternatives to Observium

Zabbix, PRTG, Nagios, Cacti, and LibreNMS are the most popular alternatives and competitors to Observium.
18
58
+ 1
1

What is Observium and what are its top alternatives?

It is a low-maintenance auto-discovering network monitoring platform supporting a wide range of device types, platforms and operating systems
Observium is a tool in the Network Monitoring category of a tech stack.

Top Alternatives to Observium

  • Zabbix
    Zabbix

    Zabbix is a mature and effortless enterprise-class open source monitoring solution for network monitoring and application monitoring of millions of metrics. ...

  • PRTG
    PRTG

    It can monitor and classify system conditions like bandwidth usage or uptime and collect statistics from miscellaneous hosts as switches, routers, servers and other devices and applications. ...

  • Nagios
    Nagios

    Nagios is a host/service/network monitoring program written in C and released under the GNU General Public License. ...

  • Cacti
    Cacti

    Cacti is a complete network graphing solution designed to harness the power of RRDTool's data storage and graphing functionality. Cacti provides a fast poller, advanced graph templating, multiple data acquisition methods, and user management features out of the box. ...

  • LibreNMS
    LibreNMS

    It is an auto-discovering PHP/MySQL/SNMP based network monitoring which includes support for a wide range of network hardware and operating systems including Cisco, Linux, FreeBSD, Juniper, Brocade, Foundry, HP and many more. ...

  • Prometheus
    Prometheus

    Prometheus is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true. ...

  • New Relic
    New Relic

    The world’s best software and DevOps teams rely on New Relic to move faster, make better decisions and create best-in-class digital experiences. If you run software, you need to run New Relic. More than 50% of the Fortune 100 do too. ...

  • Kibana
    Kibana

    Kibana is an open source (Apache Licensed), browser based analytics and search dashboard for Elasticsearch. Kibana is a snap to setup and start using. Kibana strives to be easy to get started with, while also being flexible and powerful, just like Elasticsearch. ...

Observium alternatives & related posts

Zabbix logo

Zabbix

684
66
Track, record, alert and visualize performance and availability of IT resources
684
66
PROS OF ZABBIX
  • 21
    Free
  • 9
    Alerts
  • 5
    Service/node/network discovery
  • 5
    Templates
  • 4
    Base metrics from the box
  • 3
    Multi-dashboards
  • 3
    SMS/Email/Messenger alerts
  • 2
    Grafana plugin available
  • 2
    Supports Graphs ans screens
  • 2
    Support proxies (for monitoring remote branches)
  • 1
    Perform website checking (response time, loading, ...)
  • 1
    API available for creating own apps
  • 1
    Templates free available (Zabbix Share)
  • 1
    Works with multiple databases
  • 1
    Advanced integrations
  • 1
    Supports multiple protocols/agents
  • 1
    Complete Logs Report
  • 1
    Open source
  • 1
    Supports large variety of Operating Systems
  • 1
    Supports JMX (Java, Tomcat, Jboss, ...)
CONS OF ZABBIX
  • 5
    The UI is in PHP
  • 2
    Puppet module is sluggish

related Zabbix posts

Shared insights
on
DatadogDatadogZabbixZabbixCentreonCentreon

My team is divided on using Centreon or Zabbix for enterprise monitoring and alert automation. Can someone let us know which one is better? There is one more tool called Datadog that we are using for cloud assets. Of course, Datadog presents us with huge bills. So we want to have a comparative study. Suggestions and advice are welcome. Thanks!

See more
Shared insights
on
ZabbixZabbixCheckmkCheckmk

I am looking for an easy to set up and use monitoring solution for my servers and network infrastructure. What are the main differences between Checkmk and Zabbix? What would you recommend and why?

See more
PRTG logo

PRTG

56
0
A powerful & easy network monitoring software
56
0
PROS OF PRTG
    Be the first to leave a pro
    CONS OF PRTG
    • 1
      Poor search capabilities
    • 1
      Graphs are static
    • 1
      Running on windows

    related PRTG posts

    Nagios logo

    Nagios

    828
    102
    Complete monitoring and alerting for servers, switches, applications, and services
    828
    102
    PROS OF NAGIOS
    • 53
      It just works
    • 28
      The standard
    • 12
      Customizable
    • 8
      The Most flexible monitoring system
    • 1
      Huge stack of free checks/plugins to choose from
    CONS OF NAGIOS
      Be the first to leave a con

      related Nagios posts

      Conor Myhrvold
      Tech Brand Mgr, Office of CTO at Uber · | 15 upvotes · 5.3M views

      Why we spent several years building an open source, large-scale metrics alerting system, M3, built for Prometheus:

      By late 2014, all services, infrastructure, and servers at Uber emitted metrics to a Graphite stack that stored them using the Whisper file format in a sharded Carbon cluster. We used Grafana for dashboarding and Nagios for alerting, issuing Graphite threshold checks via source-controlled scripts. While this worked for a while, expanding the Carbon cluster required a manual resharding process and, due to lack of replication, any single node’s disk failure caused permanent loss of its associated metrics. In short, this solution was not able to meet our needs as the company continued to grow.

      To ensure the scalability of Uber’s metrics backend, we decided to build out a system that provided fault tolerant metrics ingestion, storage, and querying as a managed platform...

      https://eng.uber.com/m3/

      (GitHub : https://github.com/m3db/m3)

      See more
      Shared insights
      on
      PrometheusPrometheusNagiosNagios

      I am new to DevOps and looking for training in DevOps. Some institutes are offering Nagios while some Prometheus in their syllabus. Please suggest which one is being used in the industry and which one should I learn.

      See more
      Cacti logo

      Cacti

      89
      10
      Cacti stores all of the necessary information to create graphs and populate them with data in a MySQL...
      89
      10
      PROS OF CACTI
      • 3
        Free
      • 3
        Rrdtool based
      • 2
        Fast poller
      • 1
        Graphs from snmp
      • 1
        Graphs from language independent scripts
      CONS OF CACTI
        Be the first to leave a con

        related Cacti posts

        LibreNMS logo

        LibreNMS

        55
        0
        Opensource Auto-discoverying network monitoring system
        55
        0
        PROS OF LIBRENMS
          Be the first to leave a pro
          CONS OF LIBRENMS
            Be the first to leave a con

            related LibreNMS posts

            Prometheus logo

            Prometheus

            4.3K
            239
            An open-source service monitoring system and time series database, developed by SoundCloud
            4.3K
            239
            PROS OF PROMETHEUS
            • 47
              Powerful easy to use monitoring
            • 38
              Flexible query language
            • 32
              Dimensional data model
            • 27
              Alerts
            • 23
              Active and responsive community
            • 22
              Extensive integrations
            • 19
              Easy to setup
            • 12
              Beautiful Model and Query language
            • 7
              Easy to extend
            • 6
              Nice
            • 3
              Written in Go
            • 2
              Good for experimentation
            • 1
              Easy for monitoring
            CONS OF PROMETHEUS
            • 12
              Just for metrics
            • 6
              Bad UI
            • 6
              Needs monitoring to access metrics endpoints
            • 4
              Not easy to configure and use
            • 3
              Supports only active agents
            • 2
              Written in Go
            • 2
              TLS is quite difficult to understand
            • 2
              Requires multiple applications and tools
            • 1
              Single point of failure

            related Prometheus posts

            Matt Menzenski
            Senior Software Engineering Manager at PayIt · | 16 upvotes · 1.1M views

            Grafana and Prometheus together, running on Kubernetes , is a powerful combination. These tools are cloud-native and offer a large community and easy integrations. At PayIt we're using exporting Java application metrics using a Dropwizard metrics exporter, and our Node.js services now use the prom-client npm library to serve metrics.

            See more
            Conor Myhrvold
            Tech Brand Mgr, Office of CTO at Uber · | 15 upvotes · 5.3M views

            Why we spent several years building an open source, large-scale metrics alerting system, M3, built for Prometheus:

            By late 2014, all services, infrastructure, and servers at Uber emitted metrics to a Graphite stack that stored them using the Whisper file format in a sharded Carbon cluster. We used Grafana for dashboarding and Nagios for alerting, issuing Graphite threshold checks via source-controlled scripts. While this worked for a while, expanding the Carbon cluster required a manual resharding process and, due to lack of replication, any single node’s disk failure caused permanent loss of its associated metrics. In short, this solution was not able to meet our needs as the company continued to grow.

            To ensure the scalability of Uber’s metrics backend, we decided to build out a system that provided fault tolerant metrics ingestion, storage, and querying as a managed platform...

            https://eng.uber.com/m3/

            (GitHub : https://github.com/m3db/m3)

            See more
            New Relic logo

            New Relic

            21K
            1.9K
            New Relic is the industry’s largest and most comprehensive cloud-based observability platform.
            21K
            1.9K
            PROS OF NEW RELIC
            • 414
              Easy setup
            • 344
              Really powerful
            • 245
              Awesome visualization
            • 194
              Ease of use
            • 151
              Great ui
            • 106
              Free tier
            • 80
              Great tool for insights
            • 66
              Heroku Integration
            • 55
              Market leader
            • 49
              Peace of mind
            • 21
              Push notifications
            • 20
              Email notifications
            • 17
              Heroku Add-on
            • 16
              Error Detection and Alerting
            • 13
              Multiple language support
            • 11
              SQL Analysis
            • 11
              Server Resources Monitoring
            • 9
              Transaction Tracing
            • 8
              Apdex Scores
            • 8
              Azure Add-on
            • 7
              Analysis of CPU, Disk, Memory, and Network
            • 7
              Detailed reports
            • 6
              Performance of External Services
            • 6
              Error Analysis
            • 6
              Application Availability Monitoring and Alerting
            • 6
              Application Response Times
            • 5
              Most Time Consuming Transactions
            • 5
              JVM Performance Analyzer (Java)
            • 4
              Browser Transaction Tracing
            • 4
              Top Database Operations
            • 4
              Easy to use
            • 3
              Application Map
            • 3
              Weekly Performance Email
            • 3
              Pagoda Box integration
            • 3
              Custom Dashboards
            • 2
              Easy to setup
            • 2
              Background Jobs Transaction Analysis
            • 2
              App Speed Index
            • 1
              Super Expensive
            • 1
              Team Collaboration Tools
            • 1
              Metric Data Retention
            • 1
              Metric Data Resolution
            • 1
              Worst Transactions by User Dissatisfaction
            • 1
              Real User Monitoring Overview
            • 1
              Real User Monitoring Analysis and Breakdown
            • 1
              Time Comparisons
            • 1
              Access to Performance Data API
            • 1
              Incident Detection and Alerting
            • 1
              Best of the best, what more can you ask for
            • 1
              Best monitoring on the market
            • 1
              Rails integration
            • 1
              Free
            • 0
              Proce
            • 0
              Price
            • 0
              Exceptions
            • 0
              Cost
            CONS OF NEW RELIC
            • 20
              Pricing model doesn't suit microservices
            • 10
              UI isn't great
            • 7
              Expensive
            • 7
              Visualizations aren't very helpful
            • 5
              Hard to understand why things in your app are breaking

            related New Relic posts

            Farzeem Diamond Jiwani
            Software Engineer at IVP · | 8 upvotes · 1.6M views

            Hey there! We are looking at Datadog, Dynatrace, AppDynamics, and New Relic as options for our web application monitoring.

            Current Environment: .NET Core Web app hosted on Microsoft IIS

            Future Environment: Web app will be hosted on Microsoft Azure

            Tech Stacks: IIS, RabbitMQ, Redis, Microsoft SQL Server

            Requirement: Infra Monitoring, APM, Real - User Monitoring (User activity monitoring i.e., time spent on a page, most active page, etc.), Service Tracing, Root Cause Analysis, and Centralized Log Management.

            Please advise on the above. Thanks!

            See more
            Shared insights
            on
            New RelicNew RelicKibanaKibana

            I need to choose a monitoring tool for my project, but currently, my application doesn't have much load or many users. My application is not generating GBs of data. We don't want to send the user information to New Relic because it's a 3rd party tool. And we can deploy Kibana locally on our server. What should I use, Kibana or New Relic?

            See more
            Kibana logo

            Kibana

            20.6K
            262
            Visualize your Elasticsearch data and navigate the Elastic Stack
            20.6K
            262
            PROS OF KIBANA
            • 88
              Easy to setup
            • 65
              Free
            • 45
              Can search text
            • 21
              Has pie chart
            • 13
              X-axis is not restricted to timestamp
            • 9
              Easy queries and is a good way to view logs
            • 6
              Supports Plugins
            • 4
              Dev Tools
            • 3
              More "user-friendly"
            • 3
              Can build dashboards
            • 2
              Out-of-Box Dashboards/Analytics for Metrics/Heartbeat
            • 2
              Easy to drill-down
            • 1
              Up and running
            CONS OF KIBANA
            • 7
              Unintuituve
            • 4
              Works on top of elastic only
            • 4
              Elasticsearch is huge
            • 3
              Hardweight UI

            related Kibana posts

            Tymoteusz Paul
            Devops guy at X20X Development LTD · | 23 upvotes · 10.4M views

            Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

            It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

            I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

            We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

            If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

            The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

            Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

            See more
            Tassanai Singprom

            This is my stack in Application & Data

            JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

            My Utilities Tools

            Google Analytics Postman Elasticsearch

            My Devops Tools

            Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

            My Business Tools

            Slack

            See more