Notifications

Muerte Cloud can tell you about deploys, service health and billing by email or through the Telegram bot. This page covers what events are emitted, where they can go, and how to keep the channel you use quiet enough to actually read.

Notifications are configured per workspace and can be overridden per service. Email and Telegram are independent — you can keep deploy failures in Telegram for a fast glance while a daily summary goes to email.

Two levels: workspace and service

Workspace-level rules apply to every service by default. Add a service-level override when one project should stay louder (or quieter) than the rest.

Events you can subscribe to#

Field	Description
deploy.started	A new build entered the pipeline. Includes commit SHA, author and trigger source.
deploy.succeeded	The new release passed its health check and is now serving traffic.
deploy.failed	The build, pre-deploy or start command exited non-zero. Previous release keeps serving.
deploy.cancelled	A queued deploy was cancelled by a newer one or by an operator.
service.unhealthy	Consecutive health checks failed. Instance is being replaced.
service.recovered	Health checks are passing again after an unhealthy window.
cron.failed	A scheduled cron invocation exited non-zero or timed out.
billing.limit	Workspace spend crossed a threshold you configured (50 / 80 / 100% of balance).

Delivery channels#

Per-user opt-in for each event category. Digest mode collapses noisy events into a single hourly summary.

Telegram bot

Link your workspace to @MuerteCloudBot once and get the same event categories pushed straight to your chat.

Configuring channels#

Open Workspace settings → Notifications. Email is on by default for every member; to add Telegram, click Connect Telegram, open the generated link in Telegram and confirm the pairing code in the bot chat. Once connected, pick which event categories go to each channel — defaults are safe: failures on, successes off, digest on for email. Open a service's Settings tab to override categories for that project only.

Billing alerts#

Billing notifications fire automatically as your prepaid balance is spent down — no extra setup beyond having a channel connected.

Field	Description
50%	Heads-up that half of the current balance has been used.
80%	Balance is getting low; top up soon to avoid service suspension.
100%	Balance is exhausted. Services may be suspended until you top up.

Keeping it readable#

Mute previews

Non-production services only need failure notifications. Mute deploy.succeeded on services tagged preview.

Digest mode

Collapse successful deploys into a single hourly email. Available on the email channel only.

See related settings in How deploys work and Environment variables.