[TT-17927] Update documentation for master - #2796
Open
probelabs[bot] wants to merge 17 commits into
Open
probelabs / Visor: performance
succeeded
Aug 31, 2026 in 37s
✅ Check Passed (Warnings Found)
performance check passed. Found 1 warning, but fail_if condition was not met.
Details
📊 Summary
- Total Issues: 1
- Warning Issues: 1
🔍 Failure Condition Results
Passed Conditions
- global_fail_if: Condition passed
Issues by Category
Performance (1)
⚠️ snippets/dashboard-config.mdx:165 - The documentation forstorage.main.postgres.max_open_connectionsspecifies that the default value of 0 means an unlimited number of open connections. This default can be dangerous in production as it may lead to database connection exhaustion under high load, causing severe performance degradation or service failure. The documentation should include a warning about this risk and guide users to set an appropriate limit.
Powered by Visor from Probelabs
💡 TIP: You can chat with Visor using /visor ask <your question>
Annotations
Check warning on line 165 in snippets/dashboard-config.mdx
probelabs / Visor: performance
performance Issue
The documentation for `storage.main.postgres.max_open_connections` specifies that the default value of 0 means an unlimited number of open connections. This default can be dangerous in production as it may lead to database connection exhaustion under high load, causing severe performance degradation or service failure. The documentation should include a warning about this risk and guide users to set an appropriate limit.
Raw output
Update the description to warn users about the risks of an unlimited connection pool in production environments and recommend tuning this value. This same issue is present for `storage.analytics.postgres.max_open_connections` (line 280), `storage.logs.postgres.max_open_connections` (line 395), and `storage.uptime.postgres.max_open_connections` (line 510).
Loading