Deployment failures
If a deployment fails, check the build logs first:
nexatech logs --deployment latest --stage buildCommon causes: missing environment variables, Docker build errors, failed health checks.
High latency
Use the distributed trace view to find the slowest span in a request. Sort by duration descending. Common culprits: N+1 database queries, missing indexes, synchronous external API calls in the hot path.
Memory leaks
nexatech metrics --service my-service --metric memory.rss --window 24hA steadily rising RSS over 24+ hours without a corresponding increase in traffic is a memory leak. Take a heap snapshot with nexatech debug heap-dump --service my-service.
Getting help
Open a support ticket from the dashboard (Pro and above) or post in the community forum. Include: your service ID, the time range of the issue, and any relevant logs.