Set the Proxy for Sentry Node's Event Delivery

Use transportOptions.proxy for outgoing telemetry, and check matching bypasses if the selected proxy is not contacted.

import * as Sentry from "@sentry/node";

Sentry.init({
  dsn: process.env.SENTRY_DSN,
  transportOptions: {
    proxy: "http://proxy.example.net:8080",
  },
});

This initializes the modern @sentry/node transport using the application's existing DSN. The proxy belongs under transportOptions; the HTTP proxy list provides public HTTP candidates for that endpoint value.

For an older configuration, Sentry's v7 migration moved httpProxy and httpsProxy into this single option. Use the interface for the project's SDK generation rather than combining both forms.

If event delivery does not contact the proxy, inspect the deployed transport version's supported environment inputs and no_proxy bypasses. A matching bypass can apply even with the explicit endpoint.

Evaluate Sentry's event connection separately from the application's API requests. Tracing those requests records activity; it does not give the telemetry transport control over their network routes.

Erthyglow kevrennek