Displaying 1 to 7 from 7 results

opencensus-go - A stats collection and distributed tracing framework

  •    Go

OpenCensus Go is a Go implementation of OpenCensus, a toolkit for collecting application performance and behavior monitoring data. Currently it consists of three major components: tags, stats, and tracing. The API of this project is still evolving, see: Deprecation Policy. The use of vendoring or a dependency management tool is recommended.

jaeger-client-csharp - C# client (tracer) for Jaeger

  •    CSharp

This library is still under construction and needs to be peer reviewed as well as have features added. This package contains everything you need to get up and running. If you want to report to a system such as Jaeger or Zipkin you will need to use their NuGet packages.

spark-dependencies - Spark job for dependency links

  •    Java

This is a Spark job that collects spans from storage, analyze links between services, and stores them for later presentation in the UI. Note that it is needed for the production deployment. all-in-one distribution does not need this job. This job parses all traces on a given day, based on UTC. By default, it processes the current day, but other days can be explicitly specified.

nginx-opentracing - NGINX plugin for OpenTracing

  •    C++

Enable requests served by nginx for distributed tracing via The OpenTracing Project. For linux-x86_64, pre-compiled binaries are provided for the supported versions of NGINX. These can be dropped into existing NGINX installations provided that NGINX was compiled with the --with-compat option. See example/trivial/ubuntu-x86_64 for an example of how to set it up.

tracing-examples - Examples of using third-party tracers with SignalFx

  •    Java

SignalFx Distributed Tracing intends to be instrumentation agnostic; supporting & ingesting variety of popular open instrumentation libraries including OpenTracing, Zipkin & OpenCensus. So long as the tracer configured to send spans to SignalFx ingest endpoint uses the Zipkin v1/2 JSON wire format or Jaeger Thrift format, we will accept spans irrespective of how they were instrumented - via one of the above mentioned open libraries or a homegrown one. Our goal is to build on the shoulders of giant communities rather than re-invent the wheel with proprietary libraries/agents and give customers choice to decide what works for them without worrying about vendor lock-in. For customers who have not yet instrumented their code, our default recommendation is to use OpenTracing to instrument since it has a growing ecosystem of library owners & frameworks instrumenting their code with it & use Jaeger tracer libraries to export spans to us - both of these are CNCF projects with a rapidly growing community behind them.

jaeger-operator - Jaeger Operator for Kubernetes

  •    Go

The instructions from the previous section also work on OpenShift, but make sure to install the RBAC rules, the CRD and the operator as a privileged user, such as system:admin. After the role is granted, switch back to a non-privileged user.

jaeger-client-php - Jaeger Bindings for PHP OpenTracing API

  •    PHP

This is a client-side library that can be used to instrument PHP apps for distributed trace collection, and to send those traces to Jaeger. See the OpenTracing PHP API for additional detail. Please see CONTRIBUTING.md.