Logs & Monitoring

Understand what your application is doing and troubleshoot problems quickly.

---

1. Viewing Deployment & Build Logs

Every deployment on Aureon produces a detailed log stream recording the exact build process:

1. Open your project dashboard.
2. Select any deployment from the Deployments tab.
3. The build log viewer automatically streams real-time output showing Git cloning, dependency installation, compiler output, and packaging status.

2. Reading Build Logs Effectively

When a build encounters an error, scroll through the logs to identify the first occurrence of an error line. Common indicators include:

• npm ERR! code ELIFECYCLE — A build script exited with a failure code.
• Type error: ... — TypeScript compiler encountered strict type errors.
• Module not found: Can't resolve 'xyz' — A package was referenced in code but omitted from package.json.
• SyntaxError: ... — Invalid JavaScript/TypeScript syntax in source files.

3. Container Runtime Logs

For applications running backend servers, runtime logs record the live output of your running container:

• Captures all console.log(), console.error(), and process output.
• Helps diagnose server crashes, unhandled exceptions, and API route failures.
• Accessible via the Runtime Logs subtab on active deployments.

4. Error Triage: Build vs. Deployment vs. Runtime

• Build Problem: Fails during the build step. Deployment never finishes and no container is created.
• Deployment Problem: Build succeeded, but the container failed to boot, bind to the designated port, or pass health checks.
• Runtime Problem: Deployment is marked ready and running, but user requests trigger 500 status codes or unhandled exceptions.

5. Monitoring Application Health

Aureon continuously monitors running containers:

• Container Health: Automatically detects deadlocked or terminated processes and attempts container restarts.
• HTTP Status Codes: Inspect response distributions to catch spikes in 4xx or 5xx client and server errors.