Security & Configuration

Perform Safe Production Profiling and Diagnostics

Collect enough production evidence to diagnose bottlenecks without creating additional load or exposing sensitive data.

Production profiling can reveal issues that do not appear in staging, but diagnostic tools can consume resources and capture sensitive information. Use a controlled approach.

Prefer low-overhead signals first

Start with metrics, sampled traces, slow-query summaries, and bounded logs. Enable deeper profiling only for a targeted service, endpoint, or time window.

Control access and capture scope

Restrict diagnostic endpoints and profiler access to authorized operators. Avoid capturing request bodies, credentials, session data, or full database values unless there is a justified and approved need.

Limit diagnostic impact

Use sampling, short capture windows, and resource limits. Monitor the service while profiling and stop if the diagnostic process worsens user impact.

Preserve evidence safely

Store diagnostic artifacts in access-controlled locations with defined retention. Remove temporary files and rotate any credentials that may have been exposed accidentally.

Checklist

  • Start with low-overhead telemetry.
  • Scope profiling to a service and time window.
  • Restrict access to diagnostic tools.
  • Exclude secrets and unnecessary personal data.
  • Monitor overhead and delete temporary artifacts.
Share this page Help other developers discover this resource.