This repository has been archived by the owner on Oct 3, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 19
opencensus web packages in npm registry #63
Comments
Good timing on the question! I just created #64 that sets up the release docs and tooling. Once that is in I can propose a release and get it approved and published. |
This is done now! The packages are on npm at version 0.0.1. I'm planning to update the docs with more info for how to use them from NPM, but the release is out. |
RenaultAI
pushed a commit
to RenaultAI/opencensus-web
that referenced
this issue
Nov 20, 2019
Instrument interceptor/opencensus with stats to record the number of received spans. This is accomplished by a helper to process spans that sends over spans even if the number of spans is 0. Also record with tag_key "opencensus_interceptor" whose value is the name of the respective interceptor. The test to ensure that 0 length spans are also added is currently disabled because: * Issue census-instrumentation/opencensus-go#862 is not yet implemented which requests that the OpenCensus-Go stats worker provide a method Flush to flush all data. Without it, metrics will contain stale data from previous tests. Add tests to lock-in this behavior. Also replace grpc.NewServer with a stats enabled server helper call. This enables tracing and metrics for each gRPC server by replacing naked usages of grpc.NewServer with the new helper function: internal.GRPCServerWithObservabilityEnabled Updates census-instrumentation#63
RenaultAI
pushed a commit
to RenaultAI/opencensus-web
that referenced
this issue
Nov 20, 2019
Trace instrument the section that performs batch uploading to the spanreceiver. The created span has a parent link from the initiating RPC's span. Added tests to ensure that these conditions always hold. Updates census-instrumentation#63
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When is the plan to publish opencensus web packages to npm registry?
The text was updated successfully, but these errors were encountered: