Sign In Register

How can we help you today?

Start a new topic
Answered

Advanced logging ideas for development, staging and production servers

I'm Interested in what other people have done regarding logging across various servers.


What I really want is a way to turn on or off some or all of my debugging logs based on some config that can be specified per server.


The two ways I can think of doing this are A) Do it code side with a .js config file that doesn't get merged/transferred when you promote code forwards towards production or B) do it dynamically with Redis keys or a MongoDB collection to specify debugging options.


I can see pros and cons to each of these methods and I'm interested to know what other people have tried.  I would probably lean towards using a MongoDB to make this a dynamic system and most likely use a meta table as they aren't promoted between 'games' automagically by the new GitHub system. I do have a concern about the overhead of reading another meta-table in every script though.


All opinions are appreciated.


Paul C


Senior Server Engineer

Hutch Games


Best Answer
Thanks for the suggestion guys,
it would be a really nice feature to have this ability so we are going to take a look into this.

-Customer Support

 


1 person has this question
1 Comment

Answer
Thanks for the suggestion guys,
it would be a really nice feature to have this ability so we are going to take a look into this.

-Customer Support

 

Login to post a comment