ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When managing Visual Studio Code in environments with strict outbound network traffic limits, reducing the frequency of HTTP requests to telemetry endpoints is a priority. The telemetry.enableTelemetry setting provides a mechanism to control the transmission of usage data and crash reports to Microsoft servers. Choosing to disable telemetry entirely eliminat
Managing data ingestion costs for low-traffic workloads requires a balance between budget constraints and telemetry visibility. In New Relic, reducing billable GB per month can be achieved through targeted Data Drop rules or probabilistic sampling. Drop rules provide a binary mechanism to discard specific, high-volume noise—such as repetitive health check te
Operators need to trace a failed VM deployment across Nova, Neutron, and Cinder logs to pinpoint where the failure occurred. Two documented mechanisms are available: the oslo.middleware.RequestID middleware that injects a request identifier into each service’s log line, and the Telemetry event pipeline that captures versioned notifications containing a reque
Scope of VSCodium's telemetry removal VSCodium is documented as a telemetry-free build of VS Code: Microsoft's data collection is disabled at build time, and the extension API is identical, so the same extensions install and run unmodified. Settings sync can also be enabled without Microsoft collecting the associated telemetry. What is less clear is the boun
Telemetry enableTelemetry setting VSCodium is marketed as a “no telemetry” edition of VS Code, yet the upstream settings schema still exposes telemetry.enableTelemetry . The goal is to determine whether setting telemetry.enableTelemetry to false truly suppresses all telemetry traffic across every VSCodium distribution (stable, insiders, nightly). The main un
Goal Emit actionable operational alerts in an Elixir application while avoiding notification noise, using only built‑in Logger levels, Telemetry events, and handler filtering. Constraints All suppression logic must rely on documented features: Logger.put_module_level/2, Logger handlers, filters, and Telemetry.attach/4. No third‑party libraries or custom exte
Diagnosing Intermittent Client-to-Server RPC Problems Nomad clients maintain long-lived, multiplexed connections to Nomad servers for RPC traffic. In environments with NAT gateways, load balancers, or firewalls that silently drop idle TCP sessions, these connections can become stale without either side noticing immediately, which is one plausible cause of in
newrelic
openstack
vscodium
elixir