Remove duplicative FINEST-level error logging in GrpcExporter

[VamshikrishnaMonagari]

The onError method in GrpcExporter logged failures twice: once at SEVERE (with the exception object) and again at FINEST. The FINEST log is redundant since anyone who configures their logging framework to display stack traces will get them from the SEVERE log's exception parameter.

HttpExporter does not have this pattern and required no changes.

Resolves #8098

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 90.31%. Comparing base (9692c2b) to head (dfd0240).
⚠️ Report is 4 commits behind head on main.

Files with missing lines	Patch %	Lines
...telemetry/exporter/internal/grpc/GrpcExporter.java	0.00%	1 Missing ⚠️

❌ Your patch status has failed because the patch coverage (0.00%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #8216      +/-   ##
============================================
- Coverage     90.33%   90.31%   -0.03%     
+ Complexity     7655     7652       -3     
============================================
  Files           843      843              
  Lines         23071    23071              
  Branches       2311     2311              
============================================
- Hits          20841    20836       -5     
- Misses         1515     1516       +1     
- Partials        715      719       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jack-berg]

We actually have inconsistent and probably bad patterns around this in other places:

In these cases we log both the exception message and record the the exception itself:

opentelemetry-java/exporters/common/src/main/java/io/opentelemetry/exporter/internal/grpc/GrpcExporter.java

Lines 133 to 134 in 9a992c2

	+ e.getMessage(),
	e);

opentelemetry-java/exporters/common/src/main/java/io/opentelemetry/exporter/internal/http/HttpExporter.java

Lines 119 to 125 in 9a992c2

	logger.log(
	Level.SEVERE,
	"Failed to export "
	+ type
	+ "s. The request could not be executed. Full error message: "
	+ e.getMessage(),
	e);

opentelemetry-java/sdk-extensions/jaeger-remote-sampler/src/main/java/io/opentelemetry/sdk/extension/trace/jaeger/sampler/JaegerRemoteSampler.java

Lines 130 to 136 in 9a992c2

	logger.log(
	Level.SEVERE,
	"Failed to execute "
	+ TYPE
	+ "s. The request could not be executed. Error message: "
	+ e.getMessage(),
	e);

In these cases we include the stringified caught exception message and don't record the exception, preventing the user from seeing the stacktrace:

opentelemetry-java/sdk-extensions/autoconfigure-spi/src/main/java/io/opentelemetry/sdk/autoconfigure/spi/internal/DefaultConfigProperties.java

Lines 184 to 185 in 9a992c2

	throw new ConfigurationException(
	"Invalid duration property " + name + "=" + value + ". " + ex.getMessage());

opentelemetry-java/sdk-extensions/autoconfigure/src/main/java/io/opentelemetry/sdk/autoconfigure/AutoConfiguredOpenTelemetrySdkBuilder.java

Lines 504 to 505 in 9a992c2

	logger.warning(
	"Error closing " + closeable.getClass().getName() + ": " + ex.getMessage());

opentelemetry-java/opentracing-shim/src/main/java/io/opentelemetry/opentracingshim/TracerShim.java

Lines 110 to 114 in 9a992c2

	logger.log(
	Level.WARNING,
	"Exception caught while extracting span context; returning null. "
	+ "Exception: [{0}] Message: [{1}]",
	new String[] {e.getClass().getName(), e.getMessage()});

opentelemetry-java/sdk-extensions/incubator/src/main/java/io/opentelemetry/sdk/extension/incubator/fileconfig/DeclarativeConfiguration.java

Lines 290 to 291 in 9a992c2

	logger.warning(
	"Error closing " + closeable.getClass().getName() + ": " + ex.getMessage());

opentelemetry-java/sdk/metrics/src/main/java/io/opentelemetry/sdk/metrics/SdkDoubleHistogram.java

Lines 97 to 98 in 9a992c2

	logger.warning("Error setting explicit bucket boundaries advice: " + e.getMessage());
	return this;

opentelemetry-java/sdk/metrics/src/main/java/io/opentelemetry/sdk/metrics/SdkLongHistogram.java

Line 102 in 9a992c2

logger.warning("Error setting explicit bucket boundaries advice: " + e.getMessage());

We should add some guidance to https://github.com/open-telemetry/opentelemetry-java/blob/main/CONTRIBUTING.md#best-practices-that-we-follow to recommend not stringifying the exception and recording the exception using dedicated log overloads.

[jack-berg]

Opened #8228 to discuss / track separately.

[otelbot]

Thank you for your contribution @VamshikrishnaMonagari! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey.