The OpenTelemetry .NET Client
Go to file
Paulo Janotti 8ed37a6f59
Organize StyleCop Settings and enable StyleCop on Tests (#715)
* Enable StyleCop rules for Test projects

This enables most of the StyleCop for test projects cleaning up any
errors as appropriate.

* Enable StyleCop rules for Test projects

This enables most of the StyleCop for test projects cleaning up any
errors as appropriate.

* Add line break at end of ruleset files

* Correct multi-line parameter after rebase
2020-06-10 12:12:13 -07:00
.config Fix code coverage (#666) 2020-05-06 17:11:38 -07:00
.github Tweaked the PR template so it uses github "fixes" keyword by default. (#657) 2020-05-02 12:43:26 -07:00
.vscode refactor!: collector to adapter (#612) 2020-04-22 14:44:55 -07:00
.vsts Fix code coverage (#666) 2020-05-06 17:11:38 -07:00
benchmarks Add a Jaeger Activity Exporter (#693) 2020-05-23 06:10:36 -07:00
build Organize StyleCop Settings and enable StyleCop on Tests (#715) 2020-06-10 12:12:13 -07:00
docs Disable Code Coverage from `dotnet test` on Windows (#682) 2020-05-18 17:21:42 -07:00
samples Organize StyleCop Settings and enable StyleCop on Tests (#715) 2020-06-10 12:12:13 -07:00
src Organize StyleCop Settings and enable StyleCop on Tests (#715) 2020-06-10 12:12:13 -07:00
test Organize StyleCop Settings and enable StyleCop on Tests (#715) 2020-06-10 12:12:13 -07:00
.editorconfig Remove spaces (#372) 2019-12-06 10:48:35 -08:00
.gitignore ref: cleanup sample (#195) 2019-08-26 17:25:14 -04:00
CHANGELOG.md Jaeger exporter implementation (#132) 2019-07-23 19:47:52 -07:00
CODEOWNERS Adding Mikel as an approver (#711) 2020-06-04 20:15:45 +01:00
CONTRIBUTING.md Disable Code Coverage from `dotnet test` on Windows (#682) 2020-05-18 17:21:42 -07:00
Directory.Build.props Fixed up some inconsistency in the meta showing up in package managers. (#659) 2020-05-04 14:22:32 -07:00
Directory.Build.targets Re-enable 1591 on Abstractions (#311) 2019-10-23 14:49:50 -07:00
LICENSE copy of OpenCensus at 0474607a16282252697f989113d68bdf71959070 2019-05-08 12:32:06 -07:00
NuGet.config Update to DiagnosticSource 5.0 preview4 (#667) 2020-05-07 15:55:31 -07:00
OpenTelemetry.proj Fix build (#548) 2020-03-24 15:40:37 -07:00
OpenTelemetry.sln Rename Adapter to Instrumentation per latest spec (#681) 2020-05-19 21:55:24 +01:00
README.md Adding Mikel as an approver (#711) 2020-06-04 20:15:45 +01:00

README.md

OpenTelemetry .NET

Gitter chat Build Status

The .NET OpenTelemetry client.

Installation

This repository includes multiple installable packages. The OpenTelemetry.Api package includes abstract classes and no-op implementations for the OpenTelemetry API specification.

The OpenTelemetry package is the reference implementation of the API.

Libraries that produce telemetry data should only depend on OpenTelemetry.Api, and defer the choice of the SDK to the application developer. Applications may depend on OpenTelemetry or another package that implements the API.

Please note that this library is currently in alpha, and shouldn't generally be used in production environments.

The API and SDK packages are available on the following NuGet feeds:

Documentation

The online documentation is available at TBD.

Compatible Exporters

See the OpenTelemetry registry for a list of exporters available.

Contributing

See CONTRIBUTING.md

We meet weekly on Tuesdays, and the time of the meeting alternates between 11AM PT and 4PM PT. The meeting is subject to change depending on contributors' availability. Check the OpenTelemetry community calendar for specific dates.

Meetings take place via Zoom video conference.

Meeting notes are available as a public Google doc. For edit access, get in touch on Gitter.

Approvers (@open-telemetry/dotnet-approvers):

Triagers:

Find more about the approver role in community repository.

Maintainers (@open-telemetry/dotnet-maintainers):

Find more about the maintainer role in community repository.

Release Schedule

OpenTelemetry .NET is under active development.

The library is not yet generally available, and releases aren't guaranteed to conform to a specific version of the specification. Future releases will not attempt to maintain backwards compatibility with previous releases. Each alpha and beta release includes significant changes to the API and SDK packages, making them incompatible with each other.

See the release notes for existing releases.

See the project milestones for details on upcoming releases. The dates and features described in issues and milestones are estimates, and subject to change.