The important part is tailoring it to your environment.
Also ask yourself if your system makes issues observable and testable. If you're spending a lot of resources on support or testing, those may be features worth adding. This is hard to quantify and defend to management, so sometimes you may just wind up working on it for your own sanity.
---
What to include in your question:
ENVIRONMENT
EXCEPTION
WHAT YOU'VE DONE to localize or investigate the problem
SERVICE NAME
URL
Before you ask Is X Down? Please take a moment to ask yourself these questions:
Is the service up? (Check Cloud Provider X, Cloud Provider Y)
Is the server up?
Which environment am I asking about?
Have I checked the logs?
Have you googled the exception?
Have you looked for code related to the exception in the codebase?
BAD: The service is down.
GOOD: When I run service ms-random locally, I get the following error.
And "How to ask questions the smart way": http://www.catb.org/~esr/faqs/smart-questions.html
The important part is tailoring it to your environment.
Also ask yourself if your system makes issues observable and testable. If you're spending a lot of resources on support or testing, those may be features worth adding. This is hard to quantify and defend to management, so sometimes you may just wind up working on it for your own sanity.
---
What to include in your question:
ENVIRONMENT
EXCEPTION
WHAT YOU'VE DONE to localize or investigate the problem
SERVICE NAME
URL
Before you ask Is X Down? Please take a moment to ask yourself these questions:
Is the service up? (Check Cloud Provider X, Cloud Provider Y)
Is the server up?
Which environment am I asking about?
Have I checked the logs?
Have you googled the exception?
Have you looked for code related to the exception in the codebase?
BAD: The service is down.
GOOD: When I run service ms-random locally, I get the following error.