Logging: capture and re-throw more clear error when sfl4j not in classpath but logging enabled. #3649
Labels
api: logging
Issues related to the Cloud Logging API.
priority: p3
Desirable enhancement or fix. May not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
context: #3403 (comment)
For scenario where customer app does not have logging dependency (SLF4J), but turns on logging via env variable, logging would fail. Currently, this would throw ClassNotFoundException.
For better customer experience, we can capture this and re-throw with more clear error message to communicate to customer.
Note: if change, this applies to both Gax and Auth. Need code changes in both repos.
The text was updated successfully, but these errors were encountered: