⚠️ Dozzle vs Dozzle Cloud and additional alerting providers

[amir20]

I have been getting a lot of requests to natively support other notification providers. That's not the intent for Dozzle. Dozzle webhooks is flexible.

I have added the following FAQ.

Why doesn't Dozzle support notifications for Slack, Discord, Telegram, email, etc. directly?

By design, Dozzle is unopinionated about where your alerts go. Instead of bundling integrations for specific notification platforms, Dozzle provides webhooks with customizable payload templates. This means you can send alerts to any service that accepts HTTP requests — Slack, Discord, Telegram, ntfy, PagerDuty, Opsgenie, or your own internal tools — without waiting for Dozzle to add explicit support.

There are a few reasons for this approach:

• Universality. Webhooks work with virtually every notification platform. Adding provider-specific integrations would cover only a fraction of what users need, while webhooks cover all of them.
• Maintenance. Each provider integration brings its own API quirks, authentication flows, rate limits, and breaking changes. Supporting them means Dozzle maintainers become responsible for debugging issues with third-party services — which is outside the scope of a log viewer.
• Simplicity. Dozzle is a lightweight, focused tool for viewing Docker logs. Keeping the notification layer generic keeps the codebase small and the project sustainable.

If you need a more opinionated experience with richer provider integrations (e.g., web push notifications, ntfy action buttons), Dozzle Cloud is designed for that.

For setting up webhooks with your preferred service, see the Alerts & Webhooks guide — it includes built-in payload templates for Slack, Discord, and ntfy that you can use as-is or customize.

I just won't have time to implement every single provider. So keep that in mind when opening feature requests.