Web site troubleshooting check list?
-
Does anyone know where I might find such a thing? I'm looking for examples of check lists or processes that I might be able to adapt to my environment. I am working with another developer on a process for addressing web site outages. I am embarrassed to admit that I have no idea where to start... I always just kind of fix things by instinct. I realize how bad this is, and there should be some kind of process. I'm looking for something similar to my mental process: 1. Check if everything is plugged in 2. Reboot the servers 3. Make sure the various machines can see the internet and each other etc, etc...
"Quality Software since 1983!"
http://www.smoothjazzy.com/ - see the "Programming" section for freeware tools and articles. -
Does anyone know where I might find such a thing? I'm looking for examples of check lists or processes that I might be able to adapt to my environment. I am working with another developer on a process for addressing web site outages. I am embarrassed to admit that I have no idea where to start... I always just kind of fix things by instinct. I realize how bad this is, and there should be some kind of process. I'm looking for something similar to my mental process: 1. Check if everything is plugged in 2. Reboot the servers 3. Make sure the various machines can see the internet and each other etc, etc...
"Quality Software since 1983!"
http://www.smoothjazzy.com/ - see the "Programming" section for freeware tools and articles.I hope you guys are not out looking on Google for it or something. You won't find it. That's why I asked here. Don't bother researching this unless you've actually seen it somewhere.
"Quality Software since 1983!"
http://www.smoothjazzy.com/ - see the "Programming" section for freeware tools and articles. -
Does anyone know where I might find such a thing? I'm looking for examples of check lists or processes that I might be able to adapt to my environment. I am working with another developer on a process for addressing web site outages. I am embarrassed to admit that I have no idea where to start... I always just kind of fix things by instinct. I realize how bad this is, and there should be some kind of process. I'm looking for something similar to my mental process: 1. Check if everything is plugged in 2. Reboot the servers 3. Make sure the various machines can see the internet and each other etc, etc...
"Quality Software since 1983!"
http://www.smoothjazzy.com/ - see the "Programming" section for freeware tools and articles.One idea would be to make your own list, like the websites that you are trying to find did. You should just be able to go through as many of the steps that you can think of, and then add more later, or as they come up. When servers go down at my place, that is how I do it. I have a common list, and then more detailed for different situations if the first doesn't solve the problem. I know that, 'Do it yourself', wasn't exactly the answer you were looking for, but someone has to do it sometime. And who better than you?
The best way to accelerate a Macintosh is at 9.8m/sec² - Marcus Dolengo
-
One idea would be to make your own list, like the websites that you are trying to find did. You should just be able to go through as many of the steps that you can think of, and then add more later, or as they come up. When servers go down at my place, that is how I do it. I have a common list, and then more detailed for different situations if the first doesn't solve the problem. I know that, 'Do it yourself', wasn't exactly the answer you were looking for, but someone has to do it sometime. And who better than you?
The best way to accelerate a Macintosh is at 9.8m/sec² - Marcus Dolengo
Thanks for your suggestion. That's exactly what I'm doing :) I just wanted to know if there might be an industry standard or something, which I could incorporate into my list.
"Quality Software since 1983!"
http://www.smoothjazzy.com/ - see the "Programming" section for freeware tools and articles.