Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add logs that give more information about why agent is shutting down #1358

Closed
joshdover opened this issue Sep 28, 2022 · 0 comments · Fixed by #1618
Closed

Add logs that give more information about why agent is shutting down #1358

joshdover opened this issue Sep 28, 2022 · 0 comments · Fixed by #1618
Assignees
Labels
estimation:Day Task that represents a day of work. Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team

Comments

@joshdover
Copy link
Contributor

joshdover commented Sep 28, 2022

Agent's shutdown sequence can be triggered by several different events, but our log messages don't indicate why the agent has decided to shutdown. This happens here:

logger.Info("Shutting down Elastic Agent and sending last events...")

This can be an issue when debugging agent problems in the wild with customers where we have limited insight into the host running the software. We should add better logging to indicate why the agent has decided to shutdown (eg. which signal was received, etc.).

On Windows in particular we need to log when Windows service control events are received along with the signals the agent is handling.

@joshdover joshdover added 8.6-candidate estimation:Day Task that represents a day of work. and removed 8.6-candidate labels Sep 28, 2022
@jlind23 jlind23 added the Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team label Sep 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
estimation:Day Task that represents a day of work. Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants