Re: [AusNOG] Status page recommendations

[Christopher Hawker]

+1 on UptimeRobot and the false positives, up to two per night. 

CH.

Sent from my iPhone

> On 23 Nov 2020, at 7:23 pm, Pete Mundy  wrote:
> 
> 
> +1 on the false positives from UR, especially so over IPv6 for us.
> 
> 
>> On 23/11/2020, at 7:19 PM, Darren Moss  wrote:
>> 
>> We were using UptimeRobot as an added 3rd party monitor for the last 5 
>> years, terminated just this month.
>> 
>> Too many false alarms and irregularities that didn't make sense. Constant 
>> up/down/up especially on proxied sites. No it wasn't ICMP rate limiting.
>> 
>> We eventually moved our external/3rd party monitoring to another platform 
>> and the false alarms went away.
>> 
>> One of the drawcards to stay with UptimeRobot was their Status Page, however 
>> the service was not reliable.
> 
> ___
> AusNOG mailing list
> AusNOG@lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Status page recommendations

[Pete Mundy]

+1 on the false positives from UR, especially so over IPv6 for us.


> On 23/11/2020, at 7:19 PM, Darren Moss  wrote:
> 
> We were using UptimeRobot as an added 3rd party monitor for the last 5 years, 
> terminated just this month.
> 
> Too many false alarms and irregularities that didn't make sense. Constant 
> up/down/up especially on proxied sites. No it wasn't ICMP rate limiting.
> 
> We eventually moved our external/3rd party monitoring to another platform and 
> the false alarms went away.
> 
> One of the drawcards to stay with UptimeRobot was their Status Page, however 
> the service was not reliable.

___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Status page recommendations

[Darren Moss]

We were using UptimeRobot as an added 3rd party monitor for the last 5 years, 
terminated just this month.

Too many false alarms and irregularities that didn't make sense. Constant 
up/down/up especially on proxied sites. No it wasn't ICMP rate limiting.

We eventually moved our external/3rd party monitoring to another platform and 
the false alarms went away.

One of the drawcards to stay with UptimeRobot was their Status Page, however 
the service was not reliable.



D.


-Original Message-
From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net] On Behalf Of Christian 
Heinrich
Sent: Monday, 23 November 2020 5:12 PM
To: Rhys Hanrahan
Cc: 
Subject: Re: [AusNOG] Status page recommendations

Rhys,

On Mon, 23 Nov 2020 at 11:09, Rhys Hanrahan  wrote:
> I’m hoping to get some recommendations on a status page product. We
> originally signed up for 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.

I use https://uptimerobot.com/status-page/


On Mon, 23 Nov 2020 at 11:09, Rhys Hanrahan  wrote:
> 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.

Their market fit is for the public to visit your status web page
rather than communicate out of band via email and SMS when the status
changes over time.


-- 
Regards,
Christian Heinrich

http://cmlh.id.au/contact
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Status page recommendations

[Christian Heinrich]

Rhys,

On Mon, 23 Nov 2020 at 11:09, Rhys Hanrahan  wrote:
> I’m hoping to get some recommendations on a status page product. We
> originally signed up for 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.

I use https://uptimerobot.com/status-page/


On Mon, 23 Nov 2020 at 11:09, Rhys Hanrahan  wrote:
> 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.

Their market fit is for the public to visit your status web page
rather than communicate out of band via email and SMS when the status
changes over time.


-- 
Regards,
Christian Heinrich

http://cmlh.id.au/contact
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Status page recommendations

[Cameron Murray]

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  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:sh...@kadeo.com.au]
> *Sent:* Monday, 23 November 2020 11:54 AM
> *To:* Rhys Hanrahan 
> *Cc:* ausnog@lists.ausnog.net
> *Subject:* Re: [AusNOG] Status page recommendations
>
>
>
> Hi Rhys
>
>
>
> Have you seen 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,  wrote:
>
> Hi Everyone!
>
>
>
> I’m hoping to get some recommendations on a status page product. We
> originally signed up for 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: supp...@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
>
> [image: 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@lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
> ___
> AusNOG mailing list
> AusNOG@lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Status page recommendations

[Rhys Hanrahan]

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:sh...@kadeo.com.au]
Sent: Monday, 23 November 2020 11:54 AM
To: Rhys Hanrahan 
Cc: ausnog@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, 
mailto:r...@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: supp...@nexusone.com.au<mailto:supp...@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@lists.ausnog.net<mailto:AusNOG@lists.ausnog.net>
http://lists.ausnog.net/mailman/listinfo/ausnog
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Status page recommendations

[Shaun Deans]

Hi Rhys

Have you seen 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,  wrote:

> Hi Everyone!
>
>
>
> I’m hoping to get some recommendations on a status page product. We
> originally signed up for 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: supp...@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
>
> [image: 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@lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

[AusNOG] Status page recommendations

[Rhys Hanrahan]

Hi Everyone!

I'm hoping to get some recommendations on a status page product. We originally 
signed up for 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: supp...@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@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog