Best of / Commands
Best Debugging Commands
12 Commands in the debugging category, ranked by GitHub stars — updated automatically as our nightly sync refreshes stats.
- 132.8K
help
Get help with FiftyOne skills, understand available workflows, and troubleshoot setup issues
- 20
investigate-sandbox
Investigate ZIA Sandbox file analysis -- check sandbox reports, quota, SSL prerequisite, and diagnose file block/quarantine issues.
- 30
investigate-alerts
Investigate active and historical ZDX alerts to understand scope, root cause, and impact.
- 40
domino-debug-proxy
Debug Domino proxy and routing issues for web applications. Analyzes vite.config.js, package.json, and app.sh for misconfigurations.
- 50
diagnose-deeptrace
Run a ZDX deep trace diagnostics session — start, analyze, or clean up deep traces for a user's device.
- 60
troubleshoot-experience
Troubleshoot a user's digital experience using ZDX scores, metrics, and network path data.
- 70
test
Run Postman collection tests, analyze results, diagnose failures, and suggest fixes.
- 80
doctor
Diagnose the Remember plugin — resolved paths, detected tools, storage mode, and whether capture is actually saving memory.
- 90
troubleshoot-user
Cross-product troubleshooting of user connectivity across ZCC, ZDX, ZPA, and ZIA.
- 100
typegen
Run Sanity TypeGen and troubleshoot type generation issues.
- 110
troubleshoot-connector
Troubleshoot ZPA App Connector issues -- enrollment, connectivity, upgrades, and resource utilization.
- 120
debug
Use Logfire traces to investigate errors and debug production issues
FAQ
How is this ranked?
By GitHub stars by default. Once a command has community reviews, its rating is shown alongside the star count on its detail page.
How often is this updated?
Star counts and READMEs refresh automatically every night via our GitHub sync.