You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, even when CLIENT_TELEMETRY_ENABLED is set to false, a TelemetryClient instance is created.
The method s addLogToBatch, sendBatch are implemented to do nothing when this parameter is set to false.
However, the singleton TelemetryThreadPool instance gets created through TelemetryThreadPool.getInstance() even when telemetry is disabled.
Instead, an instance of NoOpTelemetryClient could be used when telemetry is disabled.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Use NoOpTelemetryClient when CLIENT_IN_BAND_TELEMETRY_ENABLED is set to false
SNOW-520524: Use NoOpTelemetryClient when CLIENT_IN_BAND_TELEMETRY_ENABLED is set to false
Dec 17, 2021
Currently, even when
CLIENT_TELEMETRY_ENABLED
is set tofalse
, a TelemetryClient instance is created.The method s
addLogToBatch
,sendBatch
are implemented to do nothing when this parameter is set tofalse
.However, the singleton
TelemetryThreadPool
instance gets created throughTelemetryThreadPool.getInstance()
even when telemetry is disabled.Instead, an instance of
NoOpTelemetryClient
could be used when telemetry is disabled.The text was updated successfully, but these errors were encountered: