Alternatives to Supervisord logo

Alternatives to Supervisord

PM2, Monit, runit, Docker, and Kibana are the most popular alternatives and competitors to Supervisord.
108
81
+ 1
0

What is Supervisord and what are its top alternatives?

It allows its users to monitor and control a number of processes on UNIX-like operating systems. It shares some of the same goals of programs like launchd, daemontools, and runit. it is meant to be used to control processes related to a project or a customer, and is meant to start like any other program at boot time.
Supervisord is a tool in the Monitoring Tools category of a tech stack.
Supervisord is an open source tool with 7.3K GitHub stars and 1.2K GitHub forks. Here’s a link to Supervisord's open source repository on GitHub

Top Alternatives to Supervisord

  • PM2
    PM2

    Production process manager for Node.js apps with a built-in load balancer

  • Monit
    Monit

    It can monitor and manage distributed computer systems, conduct automatic maintenance and repair and execute meaningful causal actions in error situations. ...

  • runit
    runit

    It is a cross-platform Unix init scheme with service supervision, a replacement for sysvinit, and other init schemes. It runs on GNU/Linux, *BSD, MacOSX, Solaris, and can easily be adapted to other Unix operating systems. ...

  • Docker
    Docker

    The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere ...

  • 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. ...

  • Grafana
    Grafana

    Grafana is a general purpose dashboard and graph composer. It's focused on providing rich ways to visualize time series metrics, mainly though graphs but supports other ways to visualize data through a pluggable panel architecture. It currently has rich support for for Graphite, InfluxDB and OpenTSDB. But supports other data sources via plugins. ...

  • 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. ...

  • Nagios
    Nagios

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

Supervisord alternatives & related posts

PM2 logo

PM2

434
295
23
Ease-to-use Node.js process manager, like forever
434
295
+ 1
23
PROS OF PM2
  • 12
    Reliable
  • 9
    Easy to manage
  • 2
    Easy to use
CONS OF PM2
  • 4
    Memory leak

related PM2 posts

Monit logo

Monit

78
42
0
A free, open-source process supervision tool
78
42
+ 1
0
PROS OF MONIT
    Be the first to leave a pro
    CONS OF MONIT
      Be the first to leave a con

      related Monit posts

      runit logo

      runit

      3
      8
      0
      Cross-platform Unix init scheme with service supervision
      3
      8
      + 1
      0
      PROS OF RUNIT
        Be the first to leave a pro
        CONS OF RUNIT
          Be the first to leave a con

          related runit posts

          Docker logo

          Docker

          130.7K
          103.6K
          3.8K
          Enterprise Container Platform for High-Velocity Innovation.
          130.7K
          103.6K
          + 1
          3.8K
          PROS OF DOCKER
          • 823
            Rapid integration and build up
          • 688
            Isolation
          • 518
            Open source
          • 505
            Testa­bil­i­ty and re­pro­ducibil­i­ty
          • 459
            Lightweight
          • 217
            Standardization
          • 184
            Scalable
          • 105
            Upgrading / down­grad­ing / ap­pli­ca­tion versions
          • 87
            Security
          • 84
            Private paas environments
          • 33
            Portability
          • 25
            Limit resource usage
          • 16
            Game changer
          • 15
            I love the way docker has changed virtualization
          • 13
            Fast
          • 11
            Concurrency
          • 7
            Docker's Compose tools
          • 5
            Easy setup
          • 5
            Fast and Portable
          • 4
            Because its fun
          • 3
            Makes shipping to production very simple
          • 2
            It's dope
          • 2
            Highly useful
          • 1
            Very easy to setup integrate and build
          • 1
            Package the environment with the application
          • 1
            Does a nice job hogging memory
          • 1
            Open source and highly configurable
          • 1
            Simplicity, isolation, resource effective
          • 1
            MacOS support FAKE
          • 1
            Its cool
          • 1
            Docker hub for the FTW
          • 1
            HIgh Throughput
          CONS OF DOCKER
          • 8
            New versions == broken features
          • 6
            Unreliable networking
          • 6
            Documentation not always in sync
          • 4
            Moves quickly
          • 3
            Not Secure

          related Docker posts

          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 4.1M views

          Our whole DevOps stack consists of the following tools:

          • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
          • Respectively Git as revision control system
          • SourceTree as Git GUI
          • Visual Studio Code as IDE
          • CircleCI for continuous integration (automatize development process)
          • Prettier / TSLint / ESLint as code linter
          • SonarQube as quality gate
          • Docker as container management (incl. Docker Compose for multi-container application management)
          • VirtualBox for operating system simulation tests
          • Kubernetes as cluster management for docker containers
          • Heroku for deploying in test environments
          • nginx as web server (preferably used as facade server in production environment)
          • SSLMate (using OpenSSL) for certificate management
          • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
          • PostgreSQL as preferred database system
          • Redis as preferred in-memory database/store (great for caching)

          The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

          • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
          • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
          • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
          • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
          • Scalability: All-in-one framework for distributed systems.
          • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
          See more
          Tymoteusz Paul
          Devops guy at X20X Development LTD · | 23 upvotes · 5M 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
          Kibana logo

          Kibana

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

          related Kibana posts

          Tymoteusz Paul
          Devops guy at X20X Development LTD · | 23 upvotes · 5M 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
          Patrick Sun
          Software Engineer at Stitch Fix · | 11 upvotes · 502.9K views

          Elasticsearch's built-in visualization tool, Kibana, is robust and the appropriate tool in many cases. However, it is geared specifically towards log exploration and time-series data, and we felt that its steep learning curve would impede adoption rate among data scientists accustomed to writing SQL. The solution was to create something that would replicate some of Kibana's essential functionality while hiding Elasticsearch's complexity behind SQL-esque labels and terminology ("table" instead of "index", "group by" instead of "sub-aggregation") in the UI.

          Elasticsearch's API is really well-suited for aggregating time-series data, indexing arbitrary data without defining a schema, and creating dashboards. For the purpose of a data exploration backend, Elasticsearch fits the bill really well. Users can send an HTTP request with aggregations and sub-aggregations to an index with millions of documents and get a response within seconds, thus allowing them to rapidly iterate through their data.

          See more
          Grafana logo

          Grafana

          12.7K
          10K
          402
          Open source Graphite & InfluxDB Dashboard and Graph Editor
          12.7K
          10K
          + 1
          402
          PROS OF GRAFANA
          • 84
            Beautiful
          • 67
            Graphs are interactive
          • 57
            Free
          • 56
            Easy
          • 33
            Nicer than the Graphite web interface
          • 24
            Many integrations
          • 17
            Can build dashboards
          • 10
            Easy to specify time window
          • 9
            Dashboards contain number tiles
          • 8
            Can collaborate on dashboards
          • 5
            Open Source
          • 5
            Click and drag to zoom in
          • 5
            Integration with InfluxDB
          • 4
            Authentification and users management
          • 4
            Threshold limits in graphs
          • 3
            It is open to cloud watch and many database
          • 3
            Simple and native support to Prometheus
          • 2
            Great community support
          • 2
            Alerts
          • 2
            You can visualize real time data to put alerts
          • 2
            You can use this for development to check memcache
          • 0
            Grapsh as code
          • 0
            Plugin visualizationa
          CONS OF GRAFANA
          • 1
            No interactive query builder

          related Grafana posts

          Conor Myhrvold
          Tech Brand Mgr, Office of CTO at Uber · | 14 upvotes · 3.1M 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
          Matt Menzenski
          Senior Software Engineering Manager at PayIt · | 14 upvotes · 196.4K 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
          Prometheus logo

          Prometheus

          2.9K
          3.2K
          238
          An open-source service monitoring system and time series database, developed by SoundCloud
          2.9K
          3.2K
          + 1
          238
          PROS OF PROMETHEUS
          • 46
            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

          Conor Myhrvold
          Tech Brand Mgr, Office of CTO at Uber · | 14 upvotes · 3.1M 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
          Matt Menzenski
          Senior Software Engineering Manager at PayIt · | 14 upvotes · 196.4K 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
          Nagios logo

          Nagios

          801
          953
          102
          Complete monitoring and alerting for servers, switches, applications, and services
          801
          953
          + 1
          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 · | 14 upvotes · 3.1M 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