You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using log collection/processing software to monitor the CodeDeploy agent logs and spot errors during the deployment process.
Sometimes it is hard to tell if a particular Lifecycle Event has been processed successfully: When looking for strings that indicate failure, you cannot tell for sure if they did not occur or if the event is still running some time-consuming task and thus you need to keep on watching.
So, the feature request is as simple as: For every Lifecycle Event, write out a distinct log line like "End of LifecycleEvent" + the event name. This should happen under all conditions – successful runs of the hook scripts, failures, aborts etc.
The text was updated successfully, but these errors were encountered:
I am using log collection/processing software to monitor the CodeDeploy agent logs and spot errors during the deployment process.
Sometimes it is hard to tell if a particular Lifecycle Event has been processed successfully: When looking for strings that indicate failure, you cannot tell for sure if they did not occur or if the event is still running some time-consuming task and thus you need to keep on watching.
So, the feature request is as simple as: For every Lifecycle Event, write out a distinct log line like "End of LifecycleEvent" + the event name. This should happen under all conditions – successful runs of the hook scripts, failures, aborts etc.
The text was updated successfully, but these errors were encountered: