Alternatives to Jaeger logo

Alternatives to Jaeger

Zipkin, AppDynamics, Prometheus, OpenTracing, and Datadog are the most popular alternatives and competitors to Jaeger.
246
337
+ 1
8

What is Jaeger and what are its top alternatives?

Jaeger, a Distributed Tracing System
Jaeger is a tool in the Monitoring Tools category of a tech stack.
Jaeger is an open source tool with 14.6K GitHub stars and 1.8K GitHub forks. Here’s a link to Jaeger's open source repository on GitHub

Top Alternatives to Jaeger

  • Zipkin

    Zipkin

    It helps gather timing data needed to troubleshoot latency problems in service architectures. Features include both the collection and lookup of this data. ...

  • AppDynamics

    AppDynamics

    AppDynamics develops application performance management (APM) solutions that deliver problem resolution for highly distributed applications through transaction flow monitoring and deep diagnostics. ...

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

  • OpenTracing

    OpenTracing

    Consistent, expressive, vendor-neutral APIs for distributed tracing and context propagation. ...

  • Datadog

    Datadog

    Datadog is the leading service for cloud-scale monitoring. It is used by IT, operations, and development teams who build and operate applications that run on dynamic or hybrid cloud infrastructure. Start monitoring in minutes with Datadog! ...

  • Splunk

    Splunk

    It provides the leading platform for Operational Intelligence. Customers use it to search, monitor, analyze and visualize machine data. ...

  • Titan

    Titan

    Titan is a scalable graph database optimized for storing and querying graphs containing hundreds of billions of vertices and edges distributed across a multi-machine cluster. Titan is a transactional database that can support thousands of concurrent users executing complex graph traversals in real time. ...

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

Jaeger alternatives & related posts

Zipkin logo

Zipkin

105
105
9
A distributed tracing system
105
105
+ 1
9
PROS OF ZIPKIN
  • 9
    Open Source
CONS OF ZIPKIN
    Be the first to leave a con

    related Zipkin posts

    AppDynamics logo

    AppDynamics

    253
    494
    59
    Application management for the cloud generation
    253
    494
    + 1
    59
    PROS OF APPDYNAMICS
    • 18
      Deep code visibility
    • 11
      Powerful
    • 7
      Great visualization
    • 7
      Real-Time Visibility
    • 6
      Easy Setup
    • 5
      Comprehensive Coverage of Programming Languages
    • 3
      Deep DB Troubleshooting
    • 2
      Excellent Customer Support
    CONS OF APPDYNAMICS
    • 5
      Expensive
    • 2
      Poor to non-existent integration with aws services

    related AppDynamics posts

    Farzeem Diamond Jiwani
    Software Engineer at IVP · | 5 upvotes · 652.2K 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

    Hi Folks,

    I am trying to evaluate Site24x7 against AppDynamics, Dynatrace, and New Relic. Has anyone used Site24X7? If so, what are your opinions on the tool? I know that the license costs are very low compared to other tools in the market. Other than that, are there any major issues anyone has encountered using the tool itself?

    See more
    Prometheus logo

    Prometheus

    2.6K
    2.9K
    235
    An open-source service monitoring system and time series database, developed by SoundCloud
    2.6K
    2.9K
    + 1
    235
    PROS OF PROMETHEUS
    • 45
      Powerful easy to use monitoring
    • 38
      Flexible query language
    • 32
      Dimensional data model
    • 27
      Alerts
    • 22
      Active and responsive community
    • 21
      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
    • 11
      Just for metrics
    • 6
      Needs monitoring to access metrics endpoints
    • 6
      Bad UI
    • 3
      Not easy to configure and use
    • 2
      Requires multiple applications and tools
    • 2
      Written in Go
    • 2
      Supports only active agents
    • 1
      TLS is quite difficult to understand

    related Prometheus posts

    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 14 upvotes · 2.9M 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 · | 12 upvotes · 77K 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
    OpenTracing logo

    OpenTracing

    84
    87
    0
    Consistent, expressive, vendor-neutral APIs for distributed tracing and context propagation.
    84
    87
    + 1
    0
    PROS OF OPENTRACING
      Be the first to leave a pro
      CONS OF OPENTRACING
        Be the first to leave a con

        related OpenTracing posts

        Datadog logo

        Datadog

        6.1K
        5.3K
        792
        Unify logs, metrics, and traces from across your distributed infrastructure.
        6.1K
        5.3K
        + 1
        792
        PROS OF DATADOG
        • 133
          Monitoring for many apps (databases, web servers, etc)
        • 104
          Easy setup
        • 84
          Powerful ui
        • 81
          Powerful integrations
        • 68
          Great value
        • 52
          Great visualization
        • 44
          Events + metrics = clarity
        • 40
          Custom metrics
        • 39
          Notifications
        • 37
          Flexibility
        • 17
          Free & paid plans
        • 14
          Great customer support
        • 13
          Makes my life easier
        • 8
          Adapts automatically as i scale up
        • 8
          Easy setup and plugins
        • 6
          Super easy and powerful
        • 5
          In-context collaboration
        • 5
          AWS support
        • 4
          Rich in features
        • 3
          Docker support
        • 3
          Cost
        • 3
          Best than others
        • 2
          Source control and bug tracking
        • 2
          Easy to Analyze
        • 2
          Expensive
        • 2
          Cute logo
        • 2
          Good for Startups
        • 2
          Free setup
        • 2
          Monitor almost everything
        • 2
          Automation tools
        • 2
          Simple, powerful, great for infra
        • 2
          Full visibility of applications
        • 1
          Best in the field
        CONS OF DATADOG
        • 16
          Expensive
        • 3
          No errors exception tracking
        • 2
          External Network Goes Down You Wont Be Logging
        • 1
          Complicated

        related Datadog posts

        Robert Zuber

        Our primary source of monitoring and alerting is Datadog. We’ve got prebuilt dashboards for every scenario and integration with PagerDuty to manage routing any alerts. We’ve definitely scaled past the point where managing dashboards is easy, but we haven’t had time to invest in using features like Anomaly Detection. We’ve started using Honeycomb for some targeted debugging of complex production issues and we are liking what we’ve seen. We capture any unhandled exceptions with Rollbar and, if we realize one will keep happening, we quickly convert the metrics to point back to Datadog, to keep Rollbar as clean as possible.

        We use Segment to consolidate all of our trackers, the most important of which goes to Amplitude to analyze user patterns. However, if we need a more consolidated view, we push all of our data to our own data warehouse running PostgreSQL; this is available for analytics and dashboard creation through Looker.

        See more

        We are looking for a centralised monitoring solution for our application deployed on Amazon EKS. We would like to monitor using metrics from Kubernetes, AWS services (NeptuneDB, AWS Elastic Load Balancing (ELB), Amazon EBS, Amazon S3, etc) and application microservice's custom metrics.

        We are expected to use around 80 microservices (not replicas). I think a total of 200-250 microservices will be there in the system with 10-12 slave nodes.

        We tried Prometheus but it looks like maintenance is a big issue. We need to manage scaling, maintaining the storage, and dealing with multiple exporters and Grafana. I felt this itself needs few dedicated resources (at least 2-3 people) to manage. Not sure if I am thinking in the correct direction. Please confirm.

        You mentioned Datadog and Sysdig charges per host. Does it charge per slave node?

        See more
        Splunk logo

        Splunk

        459
        724
        11
        Search, monitor, analyze and visualize machine data
        459
        724
        + 1
        11
        PROS OF SPLUNK
        • 2
          API for searching logs, running reports
        • 1
          Query engine supports joining, aggregation, stats, etc
        • 1
          Query any log as key-value pairs
        • 1
          Splunk language supports string, date manip, math, etc
        • 1
          Granular scheduling and time window support
        • 1
          Alert system based on custom query results
        • 1
          Custom log parsing as well as automatic parsing
        • 1
          Dashboarding on any log contents
        • 1
          Ability to style search results into reports
        • 1
          Rich GUI for searching live logs
        CONS OF SPLUNK
        • 1
          Splunk query language rich so lots to learn

        related Splunk posts

        Shared insights
        on
        KibanaKibanaSplunkSplunkGrafanaGrafana

        I use Kibana because it ships with the ELK stack. I don't find it as powerful as Splunk however it is light years above grepping through log files. We previously used Grafana but found it to be annoying to maintain a separate tool outside of the ELK stack. We were able to get everything we needed from Kibana.

        See more
        Titan logo

        Titan

        35
        49
        0
        Distributed Graph Database
        35
        49
        + 1
        0
        PROS OF TITAN
          Be the first to leave a pro
          CONS OF TITAN
            Be the first to leave a con

            related Titan posts

            Kibana logo

            Kibana

            14.8K
            11.4K
            255
            Visualize your Elasticsearch data and navigate the Elastic Stack
            14.8K
            11.4K
            + 1
            255
            PROS OF KIBANA
            • 88
              Easy to setup
            • 61
              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
              More "user-friendly"
            • 3
              Can build dashboards
            • 3
              Dev Tools
            • 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 · 4.6M 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 · 466.8K 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