[AusNOG] Status page recommendations

Mon Nov 23 13:02:12 EST 2020

Hi Rhys,

Another option is to program your network status page, network sensor, IoT device, etc, to forward your notifications according to type, to a communications service like we have at Welcorp.com. Quite a few IT solution providers use this as a work around for point one and two to get only the communications they desire.

For example if you wanted SMS alerts for maintenance, you’d just set up your system to send your maintenance email alert to phonenumber at sms.message-service.org <mailto:phonenumber at sms.message-service.org> ; or if you wanted a voice phone call for outages, you could forward those notifications to phonenumber at tts.message-service.org <mailto:phonenumber at tts.message-service.org> . If you wanted an SMS with an embedded short URL with all the engineering data from the email, you could send the email to phonenumber at linkinsms.message-service.org <mailto:phonenumber at linkinsms.message-service.org>  

At a user level, we have built in “allow” or “deny” message time windows. So if one user wants or doesn’t want alerts at night or weekend, that is easy to configure on a web interface.

John Hoffman

John.h at welcorp.com <mailto:John.h at welcorp.com> 

CEO

WEL Corporation Pty Ltd

Mob +61 427 185 038

www.welcorp.com <http://www.welcorp.com/> 

From: AusNOG <ausnog-bounces at lists.ausnog.net> On Behalf Of Cameron Murray
Sent: Monday, 23 November 2020 11:59 AM
To: Rhys Hanrahan <rhys at nexusone.com.au>
Cc: ausnog at lists.ausnog.net
Subject: Re: [AusNOG] Status page recommendations

We went with Statuspal - Might not tick all your boxes as you need to integrate Twillio for SMS but was the cheapest and allowed the addon functions to be integrated for our needs.

On Mon, Nov 23, 2020 at 11:25 AM Rhys Hanrahan <rhys at nexusone.com.au <mailto:rhys at nexusone.com.au> > wrote:

Hi Sean,

Thanks for this. I have had a look at Cachethq – it doesn’t look like it supports all the functionality I wanted, but I was thinking about modifying it, the same as you’ve suggested. The fact that it’s a Laravel app is nice!

I also thought about developing something to plug into statuspage, using web hooks to decide when to send out notifications and effectively manage our subscribers ourselves. 

The problem is we wanted something that’s not part of our infrastructure at all, and ideally doesn’t require anything custom, so it’s 100% separate to us. But some kind of custom option may prove to be the only solution, as nothing so far differentiates maintenance vs outage notifications.

Thanks,

Rhys.

From: Shaun Deans [mailto:shaun at kadeo.com.au <mailto:shaun at kadeo.com.au> ] 
Sent: Monday, 23 November 2020 11:54 AM
To: Rhys Hanrahan <rhys at nexusone.com.au <mailto:rhys at nexusone.com.au> >
Cc: ausnog at lists.ausnog.net <mailto:ausnog at lists.ausnog.net> 
Subject: Re: [AusNOG] Status page recommendations

Hi Rhys

Have you seen cachethq.io <http://cachethq.io>  ?

It may have the features and if not it's open source so you can add them.

The developer is a well known developer (core laravel team).

It would be my choice if I needed one. I didn't validate it against your feature set.

Cheers

Shaun

On Mon, 23 Nov 2020, 11:10 am Rhys Hanrahan, <rhys at nexusone.com.au <mailto:rhys at nexusone.com.au> > wrote:

Hi Everyone!

I’m hoping to get some recommendations on a status page product. We originally signed up for statuspage.io <http://statuspage.io>  because that seems by far the most popular, but were surprised to find that what I would have thought were basic features that we need, are missing.

So far I haven’t found any other product that does what we’re after, either. Hoping someone else has. In particular we are missing:

*         The ability to allow users to subscribe to maintenance events differently to outage notifications. E.g. users want SMS notifications for outages, but only email notifications for maintenance. Many people don’t want late night SMSes of regular scheduled maintenance, some do.

*         Or further to this, some users don’t want to subscribe to maintenance notifications at all, but yet do want outage notifications.

*         The other thing we’re missing is the ability to manage subscribers as contacts. E.g. instead of a list of random mobile numbers, to associate an email and mobile to a contact so we can see who it is and what company they’re from.

*         We need component/service level subscriptions, but that seems to be a standard feature all providers offer. So no problems there.

The first two items: granular subscriptions for maintenance events is really the deal breaker, and surely we aren’t the only ones who need this. Atlassian has said this is a feature request, but won’t give any details or an ETA. Managing contacts we could live without.

We really want it to be hosted on third-party infrastructure and a turnkey solution, for obvious reasons, but I’m open to looking at anything at this point.

Thanks all!

Rhys Hanrahan
Chief Information Officer
Nexus One Pty Ltd

E: support at nexusone.com.au <mailto:support at nexusone.com.au> 
P: +61 2 9191 0606
W: http://www.nexusone.com.au/
M: PO Box A356 Sydney South, NSW 1235
A: Suite 12.03, Level 12, 227 Elizabeth Street, Sydney NSW 2000

  <http://quintus.nexusone.com.au/~rhys/nexus1-email-sig.jpg> 

The information in this email and or any of the attachments may contain; a. Confidential information of Fusion Technology Solutions Pty Ltd, Nexus One Pty Ltd, or third parties; and or b. Legally privileged information of Fusion Technology Solutions Pty Ltd, Nexus One Pty Ltd, or third parties; and or c. Copyright material Fusion Technology Solutions Pty Ltd, Nexus One Pty Ltd or third parties.

If you are not an authorised recipient of this email, please contact the sender immediately by return email or by telephone on 02 91910600 and delete the email from your system.

We do not accept any liability in connection with any computer virus, data corruption, interruption or any damage generally as a result of transmission of this email.

_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net <mailto:AusNOG at lists.ausnog.net> 
http://lists.ausnog.net/mailman/listinfo/ausnog

_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net <mailto:AusNOG at lists.ausnog.net> 
http://lists.ausnog.net/mailman/listinfo/ausnog

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20201123/42e0abc4/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 122829 bytes
Desc: not available
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20201123/42e0abc4/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 7944 bytes
Desc: not available
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20201123/42e0abc4/attachment-0001.png>