[
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
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 though git.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 After some unexpected delays, I'm glad to announce that the new status.eclipse.org website is now live. Cheers, Team Lead - Release Engineering | Eclipse Foundation
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 on statuspage.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. Team Lead - Release Engineering | Eclipse Foundation
|
Attachment:
signature.asc
Description: Message signed with OpenPGP