OpenCensus
OpenCensus Kudos to whoever came up with the design and architecture of OpenCensus. Tried it for the first time yesterday and it was a great experience for me as a monitoring developer. It feels a lot more thought out and robust than other solutions.
- Ben Ripkens, Staff Software Engineer - Instana
A single distribution of libraries that automatically collects traces and metrics from your app, displays them locally, and sends them to any analysis tool. See an overview.
OpenCensus originates from Google, where a set of libraries called Census were used to automatically capture traces and metrics from services. Since going open source, the project is now composed of a group of cloud providers, application performance management vendors, and open source contributors. The project is hosted in GitHub and all work occurs there.
Contributions are highly appreciated! Please see our community page to contribute.
Standard wire protocols and consistent APIs for handling trace and metric data. A single set of libraries for many languages, including Java, C++, Go. In progress - Python, PHP, Erlang, and Ruby. Included integrations with web and RPC frameworks, democratizing good tracing and metric collection. Included exporters for storage and analysis tools. Right now the list includes Zipkin, Prometheus, Jaeger, Stackdriver, Datadog, and SignalFx. All the code is entirely open source, to easily add your own integrations and exporters. No additional server or daemon is required to support OpenCensus. In process debugging: an optional agent for displaying request and metrics data on instrumented hosts. 2018 Google Summer of Code
Key Features
Wire protocols and consistent APIs
Single set of Libraries
Integrations
Exporters
Open Source
No Add-ons Needed
Optional Agent
Get Involved - Interested in developing for OpenCensus? Here are some ideas:
Go straight to the language of your choice:
languages
