I have just released the version 0.2 of jolokiaui (https://github.com/virtualramblas/jolokiaui), a web client for the Jolokia JVM agent (https://jolokia.org/agent/jvm.html) to monitor local and remote JVMs. It is implemented in R (https://www.r-project.org/) using the Shiny framework (http://shiny.rstudio.com/). The current release is still an alpha, but new features would be added in the next months. Any feedback is welcome. Enjoy it.
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