| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
We want to disable telemetry to avoid verbose logging but do so in a safe way without triggering any internal X-Ray panic because telemetry cannot be nil.
There was a problem hiding this comment.
LGTM! 🚀
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
We want to disable telemetry to avoid verbose logging but do so in a safe way without triggering any internal X-Ray panic (nil pointer exception) because telemetry cannot be nil.
Issue
👉 We need to initialize telemetry (at least with a dummy implementation) because the X-Ray daemon internally depends on it and we preferabbly don’t want to modify the X-Ray daemon itself.
Testing
I manually tested the new init against the customer example from support with both telemetry settings, LOCALSTACK_ENABLE_XRAY_TELEMETRY=1, and disabled by default. No crashes or nil pointer exception occurs anymore.
Background
Commit where we made the telemetry init optional: f65b6ad#diff-1ecaca51fe284265507b331fce50acf4fbf6eaedf32000481d7464b7214ef666R136
Telemetry can be quite verbose (e.g., 10+ requests for a single invocation) and given we currently don't use it, we currently disable it by default. Example PutTelemetryRecords requests: