Client Logging to AWS
Code: AWS, EC2, Elastic MapReduce, Hadoop, logging, S3
Comments Off on Client Logging to AWS
Over on the BBGameZone forums helderic asked how to deal with exploits:
Lets say player A finds a exploit to duplicate a item and decides to exploit it. He continues to exploit it for a few weeks then player B finds the bug and reports it.
How would you catch player A? And what are some systems to watch/catch exploits/bugs/cheaters.
Logging Internal Server Errors
Code: 500 errors, error handling, errors, internal server errors, logging, Rails, rescue
Comments Off on Logging Internal Server Errors
A good rule of thumb for websites is that for every hundred users who runs into a bug, one will let you know. This is when the user can even recognize there’s an error because they get a big “500: Internal Server Error”. You might get more reports if you have a very small userbase who know you, but don’t count on it. You have to log errors if you want to find out about them, so here’s some code to do that in Rails.