Troubleshooting and debugging

This page collects common symptoms observed in the example environment and their likely causes, as a starting point for debugging before escalating to the platform team.

A sudden increase in API error rates is most often caused by a downstream dependency being unavailable, and is usually visible in the monitoring dashboards described in the Monitoring section. Elevated latency without an increase in errors is more often a sign of database contention.

If an application server fails to start after a deployment, check its startup logs first for a configuration value that failed to resolve — this is the most common cause in the example environment, ahead of actual application defects.