opentracing-csharp | OpenTracing API for C | REST library

by opentracing C# Version: 0.12.1 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | opentracing-csharp Summary

opentracing-csharp is a C# library typically used in Web Services, REST applications. opentracing-csharp has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

This solution includes the .NET platform API for OpenTracing.

Support

Quality

Security

License

Reuse

Support

opentracing-csharp has a low active ecosystem.

It has 492 star(s) with 68 fork(s). There are 44 watchers for this library.

It had no major release in the last 12 months.

There are 14 open issues and 57 have been closed. On average issues are closed in 189 days. There are 3 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of opentracing-csharp is 0.12.1

Quality

opentracing-csharp has 0 bugs and 0 code smells.

Security

opentracing-csharp has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

opentracing-csharp code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

opentracing-csharp is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

opentracing-csharp releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of opentracing-csharp

Get all kandi verified functions for this library.

opentracing-csharp Key Features

No Key Features are available at this moment for opentracing-csharp.

opentracing-csharp Examples and Code Snippets

No Code Snippets are available at this moment for opentracing-csharp.

Community Discussions

Trending Discussions on opentracing-csharp

OpenTracing in .NET core without taking dependency on specific solution library

QUESTION

OpenTracing in .NET core without taking dependency on specific solution library

Asked 2019-Aug-05 at 20:23

For logging in our microservice applications we simply log to stdout/console and the docker logging driver handles and redirects these logs somewhere e.g. gelf/logstash, fluentd, etc. Basically, we're following 12 factor guidelines for logging. This means that developers working on the application code don't need to know anything about the underlying logging solution (e.g. Elasticsearch, Graylog, Splunk, etc) - it's entirely an ops/configuration concern. In theory we should be able to change the underlying logging solution without any code changes.

I'd like something similar for traces and my research has led me to OpenTracing. Developers shouldn't need to know the underlying tracing solution (e.g. Jaeger, Zipkin, Elastic APM, etc) and as per logging; in theory we should be able to change the underlying tracing solution without any code changes.

I've successfully got a .NET core POC sending traces to Jaeger using the opentracing/opentracing-csharp and jaegertracing/jaeger-client-csharp libraries.

I'm still trying to fully get my head around OpenTracing, but I'm wondering if there's a way to send traces to an OpenTracing compliant API without having to take a hard dependency on a particular solution such as Jaeger (i.e. the jaeger-client-csharp library). Based on my understanding OpenTracing is just a standard. Shouldn't I just be able to configure an OpenTracing endpoint with some sampling options without needing the jaeger-client-csharp library? Or is it that the jaeger-client-csharp is not actually Jaeger specific and can actually send traces to any OpenTracing API?

Example configuration shown below, which uses jaeger client library:

...

ANSWER

Answered 2019-Aug-05 at 20:23

OpenTracing is a set of standard APIs that consistently model and describe the behavior of distributed systems)

OpenTracing did not describe how to collect, report, store or represent the data of interrelated traces and spans. It is implementation details (such as jaeger or wavefront).

jaeger-client-csharp is very jaeger-specific. But there is one exception, called zipkin which in turns is not fully OpenTracing compliant, even it has similar terms.

If you are OK with opentracing-contrib/csharp-netcore (hope you are using this library) then if you want to achieve "no code change" (in target microservice) in order to configure tracing subsystem, you should use some plug-in model.

Good news that aspnetcore has concept of hosted startup assemblies, which allow you to configure tracing system. So, you can have some library called JaegerStartup where you will implement IHostedStartup like follows:

Source https://stackoverflow.com/questions/55962977

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install opentracing-csharp

Install the NuGet package:.

Support

If you would like to contribute code you can do so through GitHub by forking the repository and sending a pull request. By contributing your code, you agree to license your contribution under the terms of the APLv2: https://github.com/opentracing/opentracing-csharp/blob/master/LICENSE.

Find more information at: