Project crash error in Logs pane: alert routing decision

Goal

Configure actionable alerts for a Glitch project that crashes or fails to start, while avoiding the default community‑centric notification noise.

Constraints

Glitch’s Logs pane shows runtime errors, but the platform offers no per‑project filter to separate operational alerts from general notifications. The built‑in notification system is geared toward comments, mentions, and invitations, not downtime or error spikes. External uptime monitors can poll the project’s public URL, yet they may misclassify a cold start after the project sleeps as a failure.

Unresolved Decision

Should the project rely on Glitch’s native notification channel—accepting the noise—or disable it entirely and employ an external monitor that can be tuned to ignore sleep‑related delays? The platform does not document a way to configure notification thresholds or routing based on log content.

Questions

1. Does Glitch provide any API or setting to filter notifications so that only operational failures are sent to a specific channel?

2. Can an external monitoring service be configured to recognize a Glitch project’s sleep cycle and avoid false positives during cold starts?

3. Is there a documented method to programmatically subscribe to the Logs pane events for real‑time alerting?