Investigating problems while using Nolio RA require certain information.
The information needed to investigate a problem is often overlooked when there is a problem because the focus is restoring the service. This often leads to frustration because problems cannot be explained - usually because the information needed is:
This frustration can be avoided by a little planning and adopting the best practices highlighted throughout this article.
Release : 6.6, 6.7
Component : CA RELEASE AUTOMATION RELEASE OPERATIONS CENTER
You cannot plan for everything. But you can plan for the following:
When opening an issue please be as specific as you can. A description of "Deployments hanging" is extremely vague. Is there anything not hanging? Is it happening everywhere (across all applications in Nolio, across all environments in Nolio)? If the answer is yes then that will likely mean we need to focus somewhere different than if the answer is no.
There are several layers in Nolio where a problem might occur. Knowing the who, what, when, where and how (if available) give insight on where to focus. Examples:
Additional information that often helpful:
Some of this "Additional Information" may not be necessary. Some of it can be collected later on during a conversation or webex. But some of it may be relevant and the purpose of having it here is to raise awareness of these things that matter. This way you can plan on being mindful of these things while evaluating the state of Nolio and reporting problems.