-
Notifications
You must be signed in to change notification settings - Fork 155
content/*: switch tutorial exporters to use open source and free exporters #343
Comments
Thank you for the report @bogdandrutu! We used Stackdriver because it has both Tracing and Metrics. We happened to be in a crunch: 2 weeks before Cloud Next 2018 which was an important event for OpenCensus so it was easier. However, great point, we should be using open source exporters that don't require accounts but also to avoid giving the false impression that this is a Google-centric project. For the choice of open source exporters, I suggest these
To also give credit, @rakyll @saturnism had all suggested this switch too. We've just been too swamped to have the time to do it. Tonight I've got some time and will spend it on this. Thanks y'all. |
Use free and open source exporters for Go quickstarts: * Prometheus for Metrics * Zipkin for Tracing This change will be replicated across most/all languages that support the above exporters. It makes the project more attractive, easier to setup and non-biased towards any company. Updates #343
I've mailed #344 which is the seed for other languages to use after that Go update. |
Use free and open source exporters for Go quickstarts: * Prometheus for Metrics * Zipkin for Tracing This change will be replicated across most/all languages that support the above exporters. It makes the project more attractive, easier to setup and non-biased towards any company. Updates #343
Use free and open source exporters for Java quickstarts: * Prometheus for stats * Zipkin for tracing This change makes the project more attractive with vendor neutrality and not locking users into paid backends, but also these exporters are free and easy to setup. Updates #343
Use free and open source exporters for Java quickstarts: * Prometheus for stats * Zipkin for tracing This change makes the project more attractive with vendor neutrality and not locking users into paid backends, but also these exporters are free and easy to setup. Updates #343
And the Java quickstarts too have been converted to use open source exporters #347 |
Turns out this issue had already been filed in August #218 but I'll close the old one since this issue is being focused on more. |
- Replace Stackdriver exporter with Zipkin exporter in tracing tutorial - Fixes census-instrumentation#343
Replace Stackdriver Trace exporter with Zipkin exporter in tracing quickstart since Zipkin is easy to setup, free, open sourced. Updates census-instrumentation#343 Updates census-instrumentation#353
OpenCensus Node's exporters have independent READMEs with simple guides trying to explain the usage. Still, I don't think that's enough. I'll try to create some quickstarts and add them to the website as soon as possible 😄 |
Please feel free to copy those guides over as PRs to the website: Prometheus and Zipkin, these are all that are needed. The problem we have is that many of those guides are written in Typescript and some of us aren't domain experts so end up being blocked. Thus it is great to hear that you'll work on them :) Thank you! |
quickstart/python: use Prometheus exporter for metrics tutorials Replace Stackdriver Metrics exporter with Prometheus exporter in metrics quickstart since Prometheus is easy to setup, free, open sourced. Updates census-instrumentation#343 fixes census-instrumentation#353
quickstart/node.js: use Zipkin exporter for tracing tutorials Replace Stackdriver exporter with Zipkin exporter in tracing quickstart since Zipkin is easy to setup, free, open sourced. Updates census-instrumentation#355 Updates census-instrumentation#343
Replace Stackdriver Metrics exporter with Prometheus exporter in metrics quickstart since Prometheus is easy to setup, free, open sourced. This change also finally completes the tutorial TODOs since the OpenCensus-Python library has recently fixed the bugs that prevented completion of the tutorials. Updates #343 Fixes #353
Someone sent me the feedback that our QuickStart sections are too GCP centric:
https://opencensus.io/quickstart/java/metrics/ - look at the big "requirements" section.
The text was updated successfully, but these errors were encountered: