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

Configurable log level for agones sidecar #971

Closed
andrehp opened this issue Jul 31, 2019 · 4 comments · Fixed by #1007
Closed

Configurable log level for agones sidecar #971

andrehp opened this issue Jul 31, 2019 · 4 comments · Fixed by #1007
Labels
area/operations Installation, updating, metrics etc kind/feature New features for Agones
Milestone

Comments

@andrehp
Copy link

andrehp commented Jul 31, 2019

Is your feature request related to a problem? Please describe.

Currently the agones sidecar logs all received Health Pings and GameServer events with the log level INFO

Describe the solution you'd like

A way to control the log level to be sent to stdout, logrus already has such a feature: SetLevel. This would allow us to set the log level to WARN or ERROR and avoid seeing these logs, which currently just make it more harder to spot relevant errors.

Additional context

I did find the issue related to logs in Stackdriver (#335), but it doesn't apply directly to our usecase, as we forward all stdout to our logging system.

@andrehp andrehp added the kind/feature New features for Agones label Jul 31, 2019
@roberthbailey
Copy link
Member

@andrehp - where would you expect to configure the log level? Would it be a per-gameserver / per-fleet configuration or would you expect it to be a cluster-wide setting?

For the first option one idea would be to add a new optional field to the GameServerSpec for sidecar configuration. It might initially only have the loglevel, but it could be extended later to add other user-configurable options.

For the second option, it could be an install time flag in the helm configuration.

Or maybe there is another place that would make more sense.

@andrehp
Copy link
Author

andrehp commented Jul 31, 2019

Hi! Thanks for the quick reply.

I was thinking about a per-fleet configuration, this would allow for different configurations for different fleets and allow us to customize the log level according to the needs of the fleet.

@roberthbailey
Copy link
Member

That was my first thought too, but I wanted to make sure I wasn't over-designing.

@aLekSer
Copy link
Collaborator

aLekSer commented Aug 21, 2019

Currently working on next option of LogLevel feature implementation:

For the first option one idea would be to add a new optional field to the GameServerSpec for sidecar configuration. It might initially only have the loglevel, but it could be extended later to add other user-configurable options.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/operations Installation, updating, metrics etc kind/feature New features for Agones
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants