Ramon
Ramon
We should also provide a recommended out-of-the-box NameFormatter that complies with https://prometheus.io/docs/practices/naming/#metric-names
The original issue is in the specs repo. This is the Go-specific part.
I understand the objection to changing the scope of this to allow complete customization of metric names. I have retitled this to focus on the bug, which is that we...
I don't think we should silently change behavior without requiring any code change. I would prefer to keep the current default and just change all the examples. Most users copy...
What do you mean by "mark it as a breaking change"? You mean a major version change i.e. we move to 1.X.Y?
This is my proposal: https://github.com/census-instrumentation/opencensus-go/pull/930
We are worried that having two trace recording APIs in this repo will cause confusion for users. We are looking for an appropriate place to put this work.
@savaki we are going to create an "opencensus-contrib" organization to put all the integrations (including exporters) and I think this can go there. You can keep the PR open for...
Once way to do this without adding the functionality to every exporter would be to implement a wrapper exporter. Perhaps we could add this wrapper to an `exporters/exporterutil` package? So...
I think all integers less than 2^52/53 can be represented exactly. Big enough not to worry about it IMO.