How to log important dropped spans errors in AsyncReporter?

We have a problem where sometimes all spans will be dropped in Stackdriver because the user might not have configured their GCP project correctly. The exception thrown will give the user instructions for how to fix it, however AsyncReporter will log these errors at debug level on this line. We had one user get blocked on this for a long time because they did not see the error; they only found it after changing the debug level to DEBUG by chance.

context: https://github.com/spring-cloud/spring-cloud-gcp/issues/1752

Is there some way to configure or override this behavior to specify that certain special errors are “fatal” or from user error and should be logged?

In this case, a StatusRuntimeException was thrown (this is a custom GRPC exception). We would like to be able to check the error code of this exception and if it is considered ‘fatal’, be able to log the error at error-level.

Is something like this possible?

[dzou]

I’ll take a look at this.

[codefromthecrypt]

actually the flush thread is single threaded… the boolean doesn’t even need to atomic or anything. should be a good first time issue