sebright2

Even if we have getState and setState methods, users may want to be able to check whether `setState(ENABLED)` will be ignored. See the discussions in #659 and #673.

@bogdandrutu Do you have any examples of use cases where users would want to distinguish between the no-op implementation and functionality turned off programmatically?

One use case for checking whether the implementation is available is performance optimizations that rely on stats, tagging, and tracing never being turned on at runtime. For example, @zhangkun83 mentioned...

Another use case is allowing libraries that depend on OpenCensus functionality to report a more specific error when an implementation isn't available.

I tried --quiet, and it seemed to only suppress the messages logged directly from Gradle, such as "`:opencensus-api:compileJava`" or "`Deprecated Gradle features were used in this build, making it incompatible...

I think gRPC should record stats with the `method` tag but not propagate it, since the server already knows what method was called and can add the tag back.