Clean, minimal docs change. The new SIGNOZ_TOKENIZER_JWT_SECRET follows the exact same generate→substitute→document pattern as the existing Nango secrets. No issues found.

  ^{｜ View workflow run ｜ pullfrog.com ｜ 𝕏}

PR Review Summary

(0) Total Issues | Risk: Low

This PR adds documentation for a new SigNoz environment variable SIGNOZ_TOKENIZER_JWT_SECRET to the self-hosting deployment guide. The change is straightforward and correctly follows existing patterns.

✅ What's Good

1. Consistent Pattern: The new variable follows the same generation pattern as existing secrets (openssl rand -base64 32)
2. Complete Change: Updates all three required places:
   • Variable generation (line 12)
   • sed replacement (line 17)
   • Echo confirmation message (line 20)
   • "Important env vars" reference section (line 28)
3. Proper Snippet Reuse: This snippet is included in 4 deployment guides (AWS EC2, Azure VM, GCP Compute Engine, Hetzner), so all are automatically updated

💭 Consider (1)

💭 1) deploy-signoz-nango.mdx Add brief context for what this secret is used for

Issue: Unlike NANGO_ENCRYPTION_KEY which has an explanatory note ("Once you create this, it cannot be edited"), SIGNOZ_TOKENIZER_JWT_SECRET is added without any context on its purpose.

Why: Self-hosting users benefit from understanding what each secret configures, especially when troubleshooting. It's unclear whether this is a SigNoz core requirement or specific to the Inkeep integration.

Fix: Consider adding a brief note after line 28, e.g.: # Required for SigNoz query-service authentication (adjust based on actual purpose).

Refs: SigNoz environment docs may have details on this variable's purpose.

Summary: Clean documentation update that correctly adds SIGNOZ_TOKENIZER_JWT_SECRET to the self-hosting setup scripts. The change follows existing patterns and updates all necessary locations. The only suggestion is optionally adding context about what this secret is used for — but this is a minor polish item that shouldn't block merge.