Srikanth Chekuri

I just want to call out couple of things based on your usage. The `Console{Trace/Metric/Log}Exporter`s primarily intended for the debugging. And `Simple{Span/Log}Processor`s are blocking and are not recommended for production...

Maybe, but we do not guarantee anything about logs SDK.

@ColeSiegelTR You don't have to do anything except setting the propagator (which you are doing already). What is the issue you are running into? Are you seeing the broken traces?

What is it specifically that py packages do that doesn't work on arm64? All packages pass the tests and those misc are integrations tests that spin up the web, db...

It's not the tests that are failing. There is some pre test setup for integration tests which requires some modification on arm to get it up before the actual tests...

@odidev there is no known arm64 image for opencensus collector. But it doesn't change anything from an exporter pov because the backend receiver is an independent component outside its scope....

I spent sometime looking into this and found that there was an import error. [`typing.NoReturn`](https://docs.python.org/3/library/typing.html#typing.NoReturn) is newly added in `3.6.2` which was the reason for error. Can you try with...

Do you want to update the docs for all exporters or just the span exporter? Please update the title to reflect that.

> Do folks think we should add this batching mechanism to the PeriodicExportingMetricReader so it can buffer spans into the exporter? How does this help? The volume of data that...

Yes, I think we already do this in some exporters which take care of some protocol/coding specific limits. I would like to hear more the batching in metrics. I am...