Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-committers] New status.eclipse.org
Hi Arthur,

Thank you for asking. Components (gerrit, www, bugzilla...) failures are not automatically posted to twitter nor to the RSS feeds. Only "incidents" are forwarded to Twitter/RSS. Incidents are created manually by the IT team (and linked to one or more components). 

In this case, an incident (https://status.eclipse.org/incidents/zm3smfr2pyk2) has been created but the creation has not been properly broadcasted to twitter/feeds.

This system is still quite new for us, so bear with us while we're getting used to properly use it. If you see any other mis-reporting, feel free to open a ticket, send a message to the cross projects mailing list or even this one.

Thanks.


Mikaël Barbero 
Team Lead - Release Engineering | Eclipse Foundation
🐦 @mikbarbero
Eclipse Foundation: The Platform for Open Innovation and Collaboration

Le 23 avr. 2020 à 10:26, Arthur van Dorp <Arthur.vanDorp@xxxxxxxxxxxxxxxx> a écrit :

Hi Mikael
 
Thanks for the new status page. When do outages get pushed to twitter and the RSS feeds? I’ve subscribed to the RSS feed and even thoughgit.eclipse.org/r shows “major outage” on the status page since more than half an hour nothing has arrived via the RSS feed so far.
 
Regards,
Arthur
 
From: eclipse.org-committers-bounces@xxxxxxxxxxx <eclipse.org-committers-bounces@xxxxxxxxxxx> On Behalf Of Mikael Barbero
Sent: Tuesday, 21 April, 2020 10:46
To: eclipse.org-committers@xxxxxxxxxxx
Subject: Re: [eclipse.org-committers] New status.eclipse.org
 
After some unexpected delays, I'm glad to announce that the new status.eclipse.org website is now live.
 
You will see that a couple of services have partial outages for a couple of minutes each day. It's a known issue tracked by https://bugs.eclipse.org/bugs/show_bug.cgi?id=562341 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=562342.
 
Don't forget to either subscribe to the RSS (https://status.eclipse.org/history.rss) or the Atom (https://status.eclipse.org/history.atom) feeds and / or to the Twitter account https://twitter.com/Eclipse_Status. Maintenance and incidents will be communicated via these channels.
 
Cheers,

Mikaël Barbero 
Team Lead - Release Engineering | Eclipse Foundation
🐦 @mikbarbero
Eclipse Foundation: The Platform for Open Innovation and Collaboration


Le 3 avr. 2020 à 11:20, Mikael Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx> a écrit :
 
Dear committers,
 
Following the outage that occurred February 7, 2020 [1], we want to improve on is how we communicate with the  committers and the community about incidents, their impacts and the estimated time until service is restored. We also would like to improve our communication about scheduled maintenances.
 
We've taken on revamping status.eclipse.org for this purpose. Early next week, it will be migrated to a new system (based onstatuspage.io). It will have a much finer grained monitoring of the various systems the IT team is managing. In addition to the advanced monitoring, the new system will let us better communicate to our community about infrastructure incidents and their resolutions.
 
Incidents and scheduled maintenances will be displayed on the new status.eclipse.org but also automatically broadcasted to RSS/Atom feeds and to a dedicated twitter account: @Eclipse_Status [2]. Feel free to follow it. These two broadcast channels should give you better insights on what's going with the Eclipse Foundation services. 
 
The new status.eclipse.org will go live early next week. We will keep you posted as soon as it's available.
 
Thanks.
 
 
Mikaël Barbero 
Team Lead - Release Engineering | Eclipse Foundation
🐦 @mikbarbero
Eclipse Foundation: The Platform for Open Innovation and Collaboration

Attachment: signature.asc
Description: Message signed with OpenPGP

Back to the top