Email Subscription on Status Page

[sjkeerthi]

⚠️ Please verify that this bug has NOT been raised before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

📝 Describe your problem

On the status page, I don't see any email Subscription while if I post any incident and update that alone should have go to the
email who have subscribed.

Where can I find this information?

🐻 Uptime-Kuma Version

1.10.2

💻 Operating System and Arch

CentOS 7

🌐 Browser

FireFox 86.0

🐋 Docker Version

20

🟩 NodeJS Version

No response

[janbaykara]

Examples from the wild:

Twist

https://status.twist.io/

Twist is cool. It allows you to subscribe via email, slack, webhook, RSS and webhook.

Github

https://www.githubstatus.com/#

Seems to use a very similar system.

Statuspage

https://metastatuspage.com/#

Huh, same deal.

[RangersMS]

Self subscribing would be awesome! E-Mail, RSS/Atom-Feed would be great for starter.

[webysther]

This feature make a lot of OSS projects move to this one.

[janbaykara]

I actually reckon that for OSS projects, https://github.com/upptime/upptime is a decent alternative as it's free and relies entirely on Github. Their use of Github issues / 'subscribe to issue' functionality for status page updates is really smart!

[Computroniks]

I will have a look into implementing some of this. I think I might start with RSS/Atom feeds first as I think that these would probably be simpler to implement and then look into other notification methods for status pages.

I think an issue we might encounter with email notifications is when we have to send them to many clients, we risk overloading the SMTP server if we are not careful. We also have to take into account privacy when storing the clients emails and the host of legislation that comes with that. Hence why I am starting with RSS feeds.

I know about #2129 but this has been stale for months with no actual changes visible so I will just create a new PR.

[CommanderStorm]

@d19dotca @Swiftnesses @RangersMS
Please avoid adding +1 comments to issues, as this makes issue management worse.
We use the 👍🏻 emojis on the issues as a way to gauge user-interest in issues.

[d19dotca]

There was no +1 comment from me, not quite sure why I was mentioned there. 🤨
If you mean me asking for an update, that's not what most would consider a +1 IMO.

My vote was already placed on the main post several months ago. This post/issue is the top 5 most popular already too. 🙂
Edit: See https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc

If you are in a position to provide an update on this one on behalf of @louislam as my earlier remark today was requesting, that'd be greatly appreciated.

[CommanderStorm]

There was no +1 comment from me, not quite sure why I was mentioned there. raised_eyebrow If you mean me asking for an update, that's not what most would consider a +1 IMO.

I am sorry, I think I was unclear in my message:
The thing I was asking about was not adding comments without any additional value to the issue (as in +1-style comments).
Asking for updates when there are important questions that need engineering (RSS Feed, GDPR/CCPA-Conformance, see comment from @Computroniks) is not helping make issues more manageable.

Note

There are no PRs in this regard, the work on this feature has not started yet.
Given that this Project is open source, this can change (maybe you or someone else can provide a PR).
Our contribution guide can be found here

Lets get this back to being productive.
Subfeautures of this feature include:

• A RSS/Atom-Feed
  • laying out the basic UI for this
  • Testable via a small unittest that ensures that this UI is navigable to and links to the correct place.
• Email notification Backend
  • just the backend to send mails
  • including email-unsubscribe/cancellation links
  • With tests that ensure that this feature works
• Admin Frontend (requirement, as this feature is essentially adding storing personally identifiable information)
  • a way to delete emails from the admin UI
  • if any other information is stored beside the email:
    • Adding a way to export this data
  • With tests that ensure that this feature works
• Email notification Frontend
  • adding the previously implemented backend to the UI laid out in the RSS Feed
  • With a unit test, that ensures that if a user submits a mail it is saved to the database
• (further down the road) maybe adding welcome emails
• (further down the road) A captcha to protect this publicly accessible form from distributing spam

RSS+Email-Backend as well as Admin+welcome emails+Email-Frontend are parametrisable

Am I missing something in this work plan?
Are there people out there who would like to tackle one of these Subfeautures?
@Computroniks you have said you would like to tackle the RSS feed, is this still correct?

[d19dotca]

Asking for updates when there are important questions that need engineering (RSS Feed, GDPR/CCPA-Conformance, see comment from @Computroniks) is not helping make issues more manageable.

IMO, there's nothing wrong with asking (as a user of this project) if there may be a desire to add this functionality this year or if it's longer off, or if it's not planned at all / won't be included in the product. For example, some comments above had suggested this is not a feature UptimeKuma should even consider, so it'd be good to know where the developers thoughts are on this one.

Given that your latest comment was productive and included a checklist of some sub-features and requesting assistance on them with some direction, I think we can agree my comment sparked that and created forward movement on this which is the desired outcome. It fills me with hope this will be included some day still.

So I think we may have to politely agree to disagree on this matter of whether my comment was considered just a "+1" or not. 😉

Are there people out there who would like to tackle one of these Subfeautures?

I'm not a developer unfortunately but would like to help if possible. I'd be happy to be a tester for example. If I can contribute any small fixes to code though I'll certainly do that too.

This post/issue is the top 5 most popular already too. slightly_smiling_face
I just fact-checked this statement. This is not true.

You're correct. I'm not sure what my sorting was on yesterday when I checked but it was high up the list at that time. I must have used the wrong emoji to sort by, that's my mistake. Sorry about that one. Either way though it's an important feature to many and a fundamental feature of pretty much any status page service out there, so hopefully this will be added in the not too distant future. 🙂 I'll help however I can.

[Computroniks]

@Computroniks you have said you would like to tackle the RSS feed, is this still correct?

Sadly other things have got in the way and have had to take priority so in the next few months it is looking fairly unlikely that I would get any work towards this done. If someone else wants to have a go then feel free, otherwise I will leave it on my to-do list and get round to it when I have some time, probably around July/August.

[Ali-Razmjoo]

Hi,

For the ones who are really in need of subscribe feature, there are two tricks;

1. Use Listmonk to create a subscription form and configure uptime Kuma to send your lists and email when an update occurs (it needs an extra plugin to support Listmonk, and I suck in JS).
2. I found an easier way (at least for me since I am using Google Workspace (GSuite)) to create a public Google group in our organization and ask users to subscribe to the group (you can create xxxx@googlegroups.com for free via a Gmail).

Just make sure that you limit the group owner to only being able to send posts. I joined via my email and created an alias in my Google Workspace admin console "uptime-kuma-notifications@mydomain.com" (well, I don't have to pay for a new user license in workspace now); and configured the SMTP notification to send emails using Amazon SES (costs around 1-2$ for 10,000 emails) from uptime-kuma-notifications@mydomain.com. It was successfully delivered to my group members. You must configure your DNS records, such as DKIM, to verify the integrity of the email.

I hope we get this feature soon so I can get rid of the Google Workspace group.

Bests, Ali.

[TargetCrafter]

I would prefer it to be a bit more detailed than the ones in Atlasian:

• When a user clicks on the subscribe button, checkboxes appear in front of the monitors so that the user can select for what monitors they would like to be notified. After this they click a confirm button after which they are asked for their email. After submitting this they get added to a list with their notification preference.
• Whenever a monitor goes offline the users that have selected to be notified will get a customized email or through another notification channel that contains what monitor is down and extra information if available.
• The users can unsubscribe by clicking a link in the email which leads them to their notification preferences.