1045471 - status.mozilla.com does not list www.seamonkey-project.org

Status: RESOLVED WONTFIX

(mozilla.org Graveyard :: Server Operations, task)

Description

[David E. Ross]

The page at <http://status.mozilla.com/> should list the following home Web pages:  
<https://www.mozilla.org/firefox/> for Firefox
<http://www.mozilla.com/thunderbird/> for Thunderbird
<http://www.seamonkey-project.org/> for SeaMonkey

Comment 1

[Rick Bryce [:rbryce]]

(In reply to David E. Ross from comment #0)
> The page at <http://status.mozilla.com/> should list the following home Web
> pages:  
> <https://www.mozilla.org/firefox/> for Firefox
> <http://www.mozilla.com/thunderbird/> for Thunderbird
> <http://www.seamonkey-project.org/> for SeaMonkey

David, The current status.mozilla.com is maxed at 25 sites and is fed by an external monitoring service. We are currently in the process of migrating to another status page system to allow more sites and better stats. 

That being said we are focused on our most critical services, in this case mozilla.org (mozilla.com forwards to Mozilla.org).  Mozilla.org is monitored internally and externally a number of ways for service reliability. Rest assured that what you see on status.mozilla.com, encompasses what needs to be online for www.mozilla.org to be fully functional. Meaning FF and Thunderbird are available for download.

This also means seamonkey-project.org, a community managed site, will not be monitored for uptime or its current status be advertised on a public status page. Seamonkey is just not a critical service offering.
Thank you for your input and continued support of the project. Be on the look out status.mozilla.com will be changing in the coming weeks.

Comment 2

[Justin Wood (:Callek)]

(In reply to Rick Bryce [:rbryce] from comment #1)
> (In reply to David E. Ross from comment #0)
> > The page at <http://status.mozilla.com/> should list the following home Web
> > pages:  
> > <https://www.mozilla.org/firefox/> for Firefox
> > <http://www.mozilla.com/thunderbird/> for Thunderbird
> > <http://www.seamonkey-project.org/> for SeaMonkey
> 
> David, The current status.mozilla.com is maxed at 25 sites and is fed by an
> external monitoring service. We are currently in the process of migrating to
> another status page system to allow more sites and better stats. 
> 
> That being said we are focused on our most critical services, in this case
> mozilla.org (mozilla.com forwards to Mozilla.org).  Mozilla.org is monitored
> internally and externally a number of ways for service reliability. Rest
> assured that what you see on status.mozilla.com, encompasses what needs to
> be online for www.mozilla.org to be fully functional. Meaning FF and
> Thunderbird are available for download.
> 
> This also means seamonkey-project.org, a community managed site, will not be
> monitored for uptime or its current status be advertised on a public status
> page. Seamonkey is just not a critical service offering.
> Thank you for your input and continued support of the project. Be on the
> look out status.mozilla.com will be changing in the coming weeks.

rbryce does the *current* or *next* monitoring service allow us to make an outage notice on such a status page, *even* if it doesn't actively monitor things?

The largest issue I saw here from SeaMonkey community is there were many people looking to status.m.o to help identify if this was a known issue.

If it doesn't can we try and discuss what mechanics finances or policy would allow an outage on our website to be reported publically here somehow (e.g. via actually monitoring or via a notice system, etc)

Comment 3

[Chris Ilias [:cilias]]

In case Rick's comment wasn't clear, https://www.mozilla.org/firefox/ and http://www.mozilla.com/thunderbird/ are already listed on status.mozilla.com under "www.mozilla.org (https)".

Comment 4

[Robert Kaiser]

Just FIWW, the DNS for seamonkey-porject.org is hosted by me (and that's where we had the outage), while the actual website is hosted by Mozilla. This doesn't change anything said above, I just wanted to clarify that for anyone stumbling over that bug at some time.