Ramon
Ramon
I created with command: ``` docker-machine create --driver xhyve xhyve-test ``` But I get stuck with this output: ``` (xhyve-test) Waiting for VM to come online... (xhyve-test) Waiting on a...
Moved from: https://github.com/census-instrumentation/opencensus-go/issues/786 This might be solved a number of ways but I wanted to capture the abstract requirement before delving in to the various ways it could be solved...
We should define a few standard tags that we believe will be generally useful and have proven to be so internally at Google. These tags include: - `originator`: the first...
Span names of HTTP server and client should contain the HTTP method. This has nice properties - fixed cardinality, defined meaning. It is at least as useful as the path.
We need guidance for how to measure latencies and time things, since this will be very common. In particular: * Guidance on what time unit to use * What measure...
Language-independent mapping of gRPC concepts onto the stats and trace APIs. This should specify at least: * Metadata names for propagation (trace, baggage?) * Metrics * Default views
I think the default sampler of 1/10k is causing a number of problems. First, users who want to initially start doing tracing want to be able to see traces without...
Through trace sampling, we might miss important traces that don't occur very frequently for example traces leading to error conditions or high latency. We should provide a facility for starting...
Original discussion at: https://github.com/census-instrumentation/opencensus-go/issues/746 Consider the example of a server that serves results either from database or a cache. One important dimension you might want to capture as part of...
Currently our gRPC and HTTP views only break down latency by method. I would like to propose adding a new view to each of {gRPC,HTTP} {client,server} default views that also...