Project

General

Profile

Bug #1079

Status page

Added by Miklos Vajna almost 3 years ago. Updated 5 months ago.

Status:
New
Priority:
Normal
Category:
-
Target version:
Team - Q4/2017
Start date:
Due date:
% Done:

0%

Estimated time:
Tags:
URL:

Description

Hi,

When something goes wrong with github, they have an externally hosted status.github.com where they point out two things:

1) Status of the system (green/red)

2) In case of red, some short comment posted by the sysadmins, i.e. some estimation about when the system will be back, what is the problem, etc.

Something like that would be wonderful to have (e.g. as status.documentfoundation.org), so that people noticing infra problems would stop coming to #tdf-infra and asking the same question again and again.

At FOSDEM2015 Alex and Christian mentioned that such an external monitoring system (or something similar) is already in place, but it's not public. Hence this bugreport. :-)

Thanks a lot,

Miklos


Related issues

Related to Infrastructure - Bug #519: rework monitoringClosed

History

#1 Updated by Florian Effenberger over 2 years ago

  • Related to Bug #519: rework monitoring added

#2 Updated by Miklos Vajna about 2 years ago

Copying from today's #tdf-infra IRC log:

14:11 <@cloph> this is in progress re the monitoring, although no ETA as to when there's a public facing status page

#3 Updated by Beluga Beluga over 1 year ago

I think this could be closed as this exists now: http://status.documentfoundation.org/

#4 Updated by Miklos Vajna over 1 year ago

I beg to disagree. The status.documentfoundation.org is nice to have, but how do I check there if e.g. the TDF sysadmins are aware that dev-downloads is done (just an example, currently it's up & running)? Check e.g. status.github.com, you can see the output of automatic monitoring there + in case something is red, they post some "we're aware of it" type messages usually by the time you notice the breakage.

#5 Updated by Beluga Beluga over 1 year ago

Maybe something for the dashboard, then.

#6 Updated by Jean Spiteri 10 months ago

Is this still valid/active? Will (or is) the dashboard public facing? Has a status site been implemented?

#7 Updated by Beluga Beluga 10 months ago

Jean Spiteri wrote:

Is this still valid/active? Will (or is) the dashboard public facing? Has a status site been implemented?

See these:
https://fosdem.org/2017/schedule/event/development_dashboard_deployment/
https://fosdem.org/2017/schedule/event/development_dashboard/

#8 Updated by Florian Effenberger 10 months ago

IMHO you're talking about http://status.documentfoundation.org ;-)

#9 Updated by Beluga Beluga 10 months ago

Florian Effenberger wrote:

IMHO you're talking about http://status.documentfoundation.org ;-)

See Miklos's comment 4.

#10 Updated by Florian Effenberger 10 months ago

  • Assignee set to Guilhem Moulin
  • Target version set to Qlater

Ok, I see, and the answer is yes and no ;-)
The idea behind status.documentfoundation.org is to have an in-time update in case something breaks, but I agree it's a bit outdated, will talk through this in today's team call

What's missing right now is the automated connection to our monitoring system
I'll add this to Guilhem's pile, but without a concrete target atm
This could also be something for infra newcomers as EasyHack maybe, to provide some automated output from our monitoring

I think the only thing missing from your idea and the status quo is the integration of the monitoring with a list of hosts - or do I miss something?

#11 Updated by Miklos Vajna 10 months ago

Correct, the status.tdf blog is nice, but if there is some private automatic monitoring already, then having part of that publicly visible would be great. This way if e.g. gerrit is down, developers can just go to that status page, and in case it's red there, then they know sysadmins are aware of the problem. (It adds to the confidence if sysadmins can write some one-liner status text next to a red item, but it's a smaller thing.)

Thanks. :-)

#12 Updated by Florian Effenberger 5 months ago

  • Target version changed from Qlater to Q4/2017

Also available in: Atom PDF