Bugzilla – Bug 10262
Need a service status page
Last modified: 2010-04-16 13:13:40 UTC
We need some kind of page on SN where you can see the status of all music services, and maybe SN itself. Some quick system of green/yellow/red icons with possible notes, i.e. "Rhapsody is currently experiencing problems" and such. This bug is about the front-end and what it should look like. Anyone want to design a nice-looking page?
Is this page intended to be published to the users?
Yeah.
We definitely need something. But rather than adding a page, I think it's fair to look at reducing the "accounts" and "browse" sections into one music services panel/page that deals with account management, status, checkout (for stores) etc. Regardless, this isn't going to happen until 8.0. Also this is a feature request/enhancement, not a bug...
I agree with weldon that this information should be incorporated into the regular player UI, but in the mean time a simple dashboard of the status of the service would be useful for everybody (support, users, etc...) Heck if it were an RSS feed, then you could look at it in information browser, etc...
I want something like this: http://system.opendns.com/
We may not want this page viewable within SN... in case SN is down or unreachable you will want to be able to see this page. Or, make an alternate page for cases of SN being down or unreachable.
I'm less concerned with reporting our own SN status, and more with reporting status of service partners. They have problems more often than we do.
Ah, understood. Nm then.
Agreed, the OpenDNS page looks like a good thing for everybody. Everything in one place. Wouldn't hurt to have some information about our three datacenters too.) Some of that specific-to-partner information can be duplicated on the browse/settings pages for the individual services when things go from green to yellow or red. Andy: I suggest that you create a draft page with the basic information that you can gather and then let Matt take a crack at making it more approachable.
Andy - is the back-end for this feature already in place? If yes - where can I find it. If not - are you going to deal with it or should I get started there too?
No, nothing is built yet. For service status I think it'll just be manually updated anyway, I don't want to try to automate it based on number of errors or anything.
Is this anything we're still targetting for Genesis?
Yes, for Genesis.
Could someone please come up with some details what actually should be on that page? Where can I gather that information? etc. etc. We've been discussing importance and form, but not content.
Punting to next release.
From the sounds of things lately you could use a status page for SqueezeNetwork itself more than anything else. Just make sure it's not hosted _on_ SqueezeNetwork. It should be housed on a machine (or cluster) of its own in a completely separate data center. By its very nature, this service must not be a part of SqueezeNetwork, so when it gets implemented can be independent of any SqueezeNetwork release. In addition to just red and green dummy lights, you would be well served to keep a running status report about service outages, ETA for fixes, planned maintenance, upgrades, etc. You could also track the status of all SB related internet services, such as the forums, bugzilla server, and the product web site.
Yes, for Genesis
Yes. Please add a status "page."
One suggestion from out Tier-1 Support group: * Add functionality to this status page to allow Twitter functionality to alert Twitter subscribers about SN issues. and/or * Allow for external updates trusted partners-- e.g. our support staff
Twitter is a good idea, although I would hesitate to implement auto-tweeting.
invalid in new app design, need to rethink...
Matt-- What change has rendered this request invalid?
(In reply to comment #22) > Matt-- What change has rendered this request invalid? It would only make sense to have this for apps you've actually installed. If I don't have rhapsody, who cares if rhapsody is running. If this is fro INTERNAL use, that's another issue. Maybe that's the intention, but nowhere in the bug is that explicitly mentioned. Finally, I have ZERO time to work on this. At worst it should be reassigned to Andy...
This bug has been fixed in the latest release of MySqueezebox.com (formally known as SqueezeNetwork)! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.
Should not have been closed. Reopening and assigning to me. I will throw together a proposal/design. Not sure when tho.
When you make a status page available, please show 30 days of history (like the opendns example). Don't assume that users that have problems always will check the status page immediately.
Adding mickey gee to the cc list. Mickey are you coordinating your similar (duplicate?) project with Dan Evans?
Ping Dan, do you still want to be having responsibility for this? Mickey, is there any progress on your similar project?
I'm probably not the correct assignee anymore. Although, I am pursuing a larger goal of getting status pages for all our online products.