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 worker&host to logging #146

Closed
wants to merge 1 commit into from
Closed

Add worker&host to logging #146

wants to merge 1 commit into from

Conversation

KeonHee
Copy link
Member

@KeonHee KeonHee commented Apr 25, 2018

We transmit logs to external platform and from there we check logs, but there is no host&worker information in the logs.

If the log contains host information, it is possible to detect duplicate active hosts with logs.

So I changed the log format.

@jasonpet
Copy link
Contributor

this breaks the kibana query for the component field. with this change it is now set to None instead of alarmsTrigger.

@jasonpet
Copy link
Contributor

@jasonpet
Copy link
Contributor

I would recommend you put this information in the message if you need it. I personally name my container name in a way that gives me the worker and host.

Copy link
Member

@csantanapr csantanapr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See @jasonpet comments

@KeonHee
Copy link
Member Author

KeonHee commented May 10, 2018

@jasonpet
Thank you for your review.

I think it is good to include workers and hosts in the logs explicitly because they are very important concepts. What do you think?

@jasonpet
Copy link
Contributor

yeah, I definitely agree that they are important for anyone using the HA support for alarms

@KeonHee KeonHee closed this Jul 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants