conduit VS jaeger

Compare conduit vs jaeger and see what are their differences.

conduit

Ultralight, security-first service mesh for Kubernetes. Main repo for Linkerd 2.x. (by linkerd)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
conduit jaeger
33 94
10,282 19,279
1.3% 1.4%
9.9 9.7
4 days ago about 19 hours ago
Go Go
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

conduit

Posts with mentions or reviews of conduit. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-03-27.
  • Optimal JMX Exposure Strategy for Kubernetes Multi-Node Architecture
    2 projects | dev.to | 27 Mar 2024
    Leverage a service mesh like Istio or Linkerd to manage communication between microservices within the Kubernetes cluster. These service meshes can be configured to intercept JMX traffic and enforce access control policies. Benefits:
  • Linkerd no longer shipping open source, stable releases
    4 projects | news.ycombinator.com | 21 Feb 2024
    Looks like CNCF waved them through Graduation anyway, let's look at policies from July 28, 2021 when they were deemed "Graduated"

    All maintainers of the LinkerD project had @boyant.io email addresses. [0] They do list 4 other members of a "Steering Committee", but LinkerD's GOVERNANCE.md gives all of the power to maintainers: [1]

    > Ideally, all project decisions are resolved by maintainer consensus. If this is not possible, maintainers may call a vote. The voting process is a simple majority in which each maintainer receives one vote.

    And CNCF Graduation policy says a project must "Have committers from at least two organizations" [2]. So it appears that the CNCF accepted the "Steering Committee" as an acceptable 2nd committer, even though the Governance policy still gave the maintainers all of the power.

    I would like to know if the Steering Committee voted to remove stable releases from an un-biased position acting in the best interest of the project, or if they were simply ignored or not even advised on the decision.

    I'm all for Boyant doing what they need to do to make money and survive as a Company. But at that point my opinion is that they should withdraw the project from the CNCF and stop pretending like the foundation has any influence on the project's governance.

    [0] https://github.com/linkerd/linkerd2/blob/489ca1e3189b6a5289d...

  • Ultimate EKS Baseline Cluster: Part 1 - Provision EKS
    17 projects | dev.to | 21 Jul 2023
    From here, we can explore other developments and tutorials on Kubernetes, such as o11y or observability (PLG, ELK, ELF, TICK, Jaeger, Pyroscope), service mesh (Linkerd, Istio, NSM, Consul Connect, Cillium), and progressive delivery (ArgoCD, FluxCD, Spinnaker).
  • Istio moved to CNCF Graduation stage
    13 projects | news.ycombinator.com | 12 Jul 2023
    https://linkerd.io/ is a much lighter-weight alternative but you do still get some of the fancy things like mtls without needing any manual configuration. Install it, label your namespaces, and let it do it's thing!
  • API release strategies with API Gateway
    5 projects | dev.to | 22 Dec 2022
    Open source API Gateway (Apache APISIX and Traefik), Service Mesh (Istio and Linkerd) solutions are capable of doing traffic splitting and implementing functionalities like Canary Release and Blue-Green deployment. With canary testing, you can make a critical examination of a new release of an API by selecting only a small portion of your user base. We will cover the canary release next section.
  • GKE with Consul Service Mesh
    29 projects | dev.to | 3 Dec 2022
    I have experimented with other service meshes and I was able to get up to speed quickly: Linkerd = 1 day, Istio = 3 days, NGINX Service Mesh = 5 days, but Consul Connect service mesh took at least 11 days to get off the ground. This is by far the most complex solution available.
  • How is a service mesh implemented on low level?
    2 projects | /r/kubernetes | 29 Nov 2022
    https://github.com/linkerd/linkerd2 (random example)
  • Kubernetes operator written in rust
    2 projects | /r/kubernetes | 9 Nov 2022
    It’s not an operator but a major component of the Linkerd control plane is written in Rust with kube-rs. https://github.com/linkerd/linkerd2/tree/main/policy-controller
    2 projects | /r/kubernetes | 9 Nov 2022
  • What is a service mesh?
    6 projects | dev.to | 24 Oct 2022
    Out of the number of service mesh solutions that exist, the most popular open source ones are: Linkerd, Istio, and Consul. Here at Koyeb, we are using Kuma.

jaeger

Posts with mentions or reviews of jaeger. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-01.
  • Show HN: An open source performance monitoring tool
    2 projects | news.ycombinator.com | 1 Feb 2024
    As engineers at past startups, we often had to debug slow queries, poor load times, inconsistent errors, etc... While tools like Jaegar [2] helped us inspect server-side performance, we had no way to tie user events to the traces we were inspecting. In other words, although we had an idea of what API route was slow, there wasn’t much visibility into the actual bottleneck.

    This is where our performance product comes in: we’re rethinking a tracing/performance tool that focuses on bridging the gap between the client and server.

    What’s unique about our approach is that we lean heavily into creating traces from the frontend. For example, if you’re using our Next.js SDK, we automatically connect browser HTTP requests with server-side code execution, all from the perspective of a user. We find this much more powerful because you can understand what part of your frontend codebase causes a given trace to occur. There’s an example here [3].

    From an instrumentation perspective, we’ve built our SDKs on-top of OTel, so you can create custom spans to expand highlight-created traces in server routes that will transparently roll up into the flame graph you see in our UI. You can also send us raw OTel traces and manually set up the client-server connection if you want. [4] Here’s an example of what a trace looks like with a database integration using our Golang GORM SDK, triggered by a frontend GraphQL query [5] [6].

    In terms of how it's built, we continue to rely heavily on ClickHouse as our time-series storage engine. Given that traces require that we also query based on an ID for specific groups of spans (more akin to an OLTP db), we’ve leveraged the power of CH materialized views to make these operations efficient (described here [7]).

    To try it out, you can spin up the project with our self hosted docs [8] or use our cloud offering at app.highlight.io. The entire stack runs in docker via a compose file, including an OpenTelemetry collector for data ingestion. You’ll need to point your SDK to export data to it by setting the relevant OTLP endpoint configuration (ie. environment variable OTEL_EXPORTER_OTLP_LOGS_ENDPOINT [9]).

    Overall, we’d really appreciate feedback on what we’re building here. We’re also all ears if anyone has opinions on what they’d like to see in a product like this!

    [1] https://github.com/highlight/highlight/blob/main/LICENSE

    [2] https://www.jaegertracing.io

    [3] https://app.highlight.io/1383/sessions/COu90Th4Qc3PVYTXbx9Xe...

    [4] https://www.highlight.io/docs/getting-started/native-opentel...

    [5] https://static.highlight.io/assets/docs/gorm.png

    [6] https://github.com/highlight/highlight/blob/1fc9487a676409f1...

    [7] https://highlight.io/blog/clickhouse-materialized-views

    [8] https://www.highlight.io/docs/getting-started/self-host/self...

    [9] https://opentelemetry.io/docs/concepts/sdk-configuration/otl...

  • Kubernetes Ingress Visibility
    2 projects | /r/kubernetes | 10 Dec 2023
    For the request following, something like jeager https://www.jaegertracing.io/, because you are talking more about tracing than necessarily logging. For just monitoring, https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack would be the starting point, then it depends. Nginx gives metrics out of the box, then you can pull in the dashboard like https://grafana.com/grafana/dashboards/14314-kubernetes-nginx-ingress-controller-nextgen-devops-nirvana/ , or full metal with something like service mesh monitoring which would provably fulfil most of the requirements
  • Migrating to OpenTelemetry
    8 projects | news.ycombinator.com | 16 Nov 2023
    Have you checked out Jaeger [1]? It is lightweight enough for a personal project, but featureful enough to really help "turn on the lightbulb" with other engineers to show them the difference between logging/monitoring and tracing.

    [1] https://www.jaegertracing.io/

  • The Road to GraphQL At Enterprise Scale
    6 projects | dev.to | 8 Nov 2023
    From the perspective of the realization of GraphQL infrastructure, the interesting direction is "Finding". How to find the problem? How to find the bottleneck of the system? Distributed Tracing System (DTS) will help answer this question. Distributed tracing is a method of observing requests as they propagate through distributed environments. In our scenario, we have dozens of subgraphs, gateway, and transport layer through which the request goes. We have several tools that can be used to detect the whole lifecycle of the request through the system, e.g. Jaeger, Zipkin or solutions that provided DTS as a part of the solution NewRelic.
  • OpenTelemetry Exporters - Types and Configuration Steps
    5 projects | dev.to | 30 Oct 2023
    Jaeger is an open-source, distributed tracing system that monitors and troubleshoots the flow of requests through complex, microservices-based applications, providing a comprehensive view of system interactions.
  • Fault Tolerance in Distributed Systems: Strategies and Case Studies
    4 projects | dev.to | 18 Oct 2023
    However, ensuring fault tolerance in distributed systems is not at all easy. These systems are complex, with multiple nodes or components working together. A failure in one node can cascade across the system if not addressed timely. Moreover, the inherently distributed nature of these systems can make it challenging to pinpoint the exact location and cause of fault - that is why modern systems rely heavily on distributed tracing solutions pioneered by Google Dapper and widely available now in Jaeger and OpenTracing. But still, understanding and implementing fault tolerance becomes not just about addressing the failure but predicting and mitigating potential risks before they escalate.
  • Observability in Action Part 3: Enhancing Your Codebase with OpenTelemetry
    3 projects | dev.to | 17 Oct 2023
    In this article, we'll use HoneyComb.io as our tracing backend. While there are other tools in the market, some of which can be run on your local machine (e.g., Jaeger), I chose HoneyComb because of their complementary tools that offer improved monitoring of the service and insights into its behavior.
  • Distributed Tracing and OpenTelemetry Guide
    5 projects | dev.to | 28 Sep 2023
    In this example, I will create 3 Node.js services (shipping, notification, and courier) using Amplication, add traces to all services, and show how to analyze trace data using Jaeger.
  • Event-Driven Architecture 101
    3 projects | dev.to | 25 Sep 2023
    For example, without investment, visibility into system behavior as a whole can be much more difficult in an event-driven system. Investing in something like Open Telemetry and a service catalog is a good idea.  Getting started with these things are relatively simple, but if you want to store your traces somewhere that are searchable, you are going to have to either pay for a SaaS tool that ingests them or you are going to have to run and maintain an open source tool capable of this such as Jaeger. For service cataloging, Backstage is becoming a very popular option.   Depending on the capabilities and the capacity of your engineering team, this might be a good option and many companies do have platform teams that provide tooling such as this. With the average salary of a platform Engineer being ~$144k, companies should think carefully on whether the benefits of an EDA are going to outweigh the cost. We will dig deeper into this in part 2 and 3 of the series.
  • The Complete Microservices Guide
    17 projects | dev.to | 21 Sep 2023
    Distributed Tracing: Middleware for distributed tracing like Jaeger and Zipkin helps monitor and trace requests as they flow through multiple microservices, aiding in debugging, performance optimization, and understanding the system's behavior.

What are some alternatives?

When comparing conduit and jaeger you can also consider the following projects:

Sentry - Developer-first error tracking and performance monitoring

skywalking - APM, Application Performance Monitoring System

prometheus - The Prometheus monitoring system and time series database.

signoz - SigNoz is an open-source observability platform native to OpenTelemetry with logs, traces and metrics in a single application. An open-source alternative to DataDog, NewRelic, etc. 🔥 🖥. 👉 Open source Application Performance Monitoring (APM) & Observability tool

Pinpoint - APM, (Application Performance Management) tool for large-scale distributed systems.

fluent-bit - Fast and Lightweight Logs and Metrics processor for Linux, BSD, OSX and Windows

hypertrace - An open source distributed tracing & observability platform

VictoriaMetrics - VictoriaMetrics: fast, cost-effective monitoring solution and time series database

Grafana - The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.

Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.

zipkin - Zipkin is a distributed tracing system

apm-server - APM Server