Advertisement
Rather than just Twitter updates.
The old Status page with all it's colorful red, yellow, green indicators gave me instantaneous real-time knowledge of the current status of the servers and the network as a whole. Without anyone having to post anything.
Now if there are problems, it's back to hoping that someone will post a message eventually. I had problems getting on earlier. But the last Twitter was from ages ago.
This is what I am seeing right now, it's just a Twitter feed:
Current Tribe.net Status: follow TribeHelp on Twitter
* new status.tribe.net page with twitter feed 2 days ago
* Intermittent issues with capacity this week, monitoring it as much as possible. No database crashes, just webserver overloads. 6 days ago
* At Open Translation Tools 09 in Amsterdam this week & giving a "speedgeek" preso tomorrow #ott09 6 days ago
* site is up, with the usual slow initial load after down time... should be back to normal in an hour or so.... 11 days ago
* installs successful, on our way back soon! 11 days ago
------
I can look that up on my own, via Twitter. If Tribe.net is down, that status page will probably be down too, making it TOTALLY USELESS!!! And it's a duplication of what already exists on Twitter.
We NEEDED the Status available in real time. I really believe that we NEEDED it, because this site has had a history of going up and down and having problems with various servers.
It would be even better if there was a way to tie the former Status into Twitter feed that would generate messages, such as:
Restart your browser and try to load the site again
or
The site is completely down
Something that would read the old Status info, and know that there was only one finicky server and that it would probably work fine if the person would restart their browser (to get on a different server perhaps).
A Twitter message from two days ago does nothing to help anyone right now who cannot get online.
The old Status page with all it's colorful red, yellow, green indicators gave me instantaneous real-time knowledge of the current status of the servers and the network as a whole. Without anyone having to post anything.
Now if there are problems, it's back to hoping that someone will post a message eventually. I had problems getting on earlier. But the last Twitter was from ages ago.
This is what I am seeing right now, it's just a Twitter feed:
Current Tribe.net Status: follow TribeHelp on Twitter
* new status.tribe.net page with twitter feed 2 days ago
* Intermittent issues with capacity this week, monitoring it as much as possible. No database crashes, just webserver overloads. 6 days ago
* At Open Translation Tools 09 in Amsterdam this week & giving a "speedgeek" preso tomorrow #ott09 6 days ago
* site is up, with the usual slow initial load after down time... should be back to normal in an hour or so.... 11 days ago
* installs successful, on our way back soon! 11 days ago
------
I can look that up on my own, via Twitter. If Tribe.net is down, that status page will probably be down too, making it TOTALLY USELESS!!! And it's a duplication of what already exists on Twitter.
We NEEDED the Status available in real time. I really believe that we NEEDED it, because this site has had a history of going up and down and having problems with various servers.
It would be even better if there was a way to tie the former Status into Twitter feed that would generate messages, such as:
Restart your browser and try to load the site again
or
The site is completely down
Something that would read the old Status info, and know that there was only one finicky server and that it would probably work fine if the person would restart their browser (to get on a different server perhaps).
A Twitter message from two days ago does nothing to help anyone right now who cannot get online.
posted by:
|
Unsubscribed |
Advertisement
Advertisement
-
-
Re: Preferred the old status page
Mon, June 29, 2009 - 11:39 AMunfortunately the software running that was complete abandonware and wasn't working very well. Many of the servers it was reporting on were not relevant anyway and the problems it indicated weren't accurate. The new servers are monitored by a different tool and weren't included in it.
It might have been pretty, but it wasn't a reflection of any sort of reality on the state of the systems at this point. -
-
Re: Preferred the old status page
Mon, June 29, 2009 - 12:00 PMAh...a placebo of sorts, then?
Funny.
It worked : )
Any chance of getting an accurate version in the future? -
-
Re: Preferred the old status page
Mon, June 29, 2009 - 12:01 PMOr at least updating the twitter page more often? -
-
Re: Preferred the old status page
Mon, June 29, 2009 - 12:50 PMOk, I just updated the twitter feed, but looks like twitter is overloaded now too... In any case, the status page is not dependent on the application servers, it just replicates the look and feel, so if the site is down, the status page is still up (unless the status server is down...) -
-
Re: Preferred the old status page
Mon, June 29, 2009 - 12:54 PM(*laughing*)
Cool...
Ah, technology....
-
-
-
-
Re: Preferred the old status page
Mon, June 29, 2009 - 12:44 PMAlso, to djarum's points... If anyone is having trouble logging in, they should just email us.
Knowing which servers are having trouble with NTP isn't going to help that in any way, but if something affecting the site is happening, we will definitely post it on twitter. Otherwise, no news is good news! -
-
Re: Preferred the old status page
Mon, June 29, 2009 - 12:48 PMOkay.
Thanks, Carolyn : )
-
-
Unsu...
Re: Preferred the old status page
Wed, July 1, 2009 - 6:10 AM" It might have been pretty, but it wasn't a reflection of any sort of reality on the state of the systems at this point. "
Oh.
Well, how about adding some nice lights to the new page? Or one of those animated glitter signatures? -
-
Re: Preferred the old status page
Thu, July 2, 2009 - 6:38 PMThe man would like flashing red and blue lights.
-
-
-
