The 200 issue of Mokabyte is online (http://www.mokabyte.it). It is the most important Italian web magazine about Java technologies and Agile methodologies. I am really proud to have given a contribution writing several articles (here's one, http://www2.mokabyte.it/cms/article.run?articleId=7TK-XI4-MRI-VMN_7f000001_13046033_40989f48) for it during the period 2006-2013 . I want to congratulate Giovanni Puliti, Francesco Saliola and all the people who made that magazine great. Thanks a lot guys!
In order to show that the considerations done in my last post are general for any log shipping purpose, let's see now how the same process applies to a more real use case scenario: the log shipping and analysis of a MongoDB database logs. MongoDB logs pattern Starting from the release 3.0 (I am considering the release 3.2 for this post) the MongoDB logs come with the following pattern: <timestamp> <severity> <component> [<context>] <message> where: timestamp is in iso8601-local format. severity is the level associated to each log message. It is a single character field. Possible values are F (Fatal), E (Error), W (Warning), I (Informational) and D (Debug). component is for a functional categorization of the log message. Please refer to the specific release of MongoDB you're using to know the full list of possible values. context is the specific context for a me...
Comments
Post a Comment