• The monitoring routine is now working with an operator pattern like the dashboard, which enable us to control the basic functions of monitoring inside other packages such as server
• To my knowledge it didn't introduce any race-cond as the operator is mutexed and locked for every read/write operation on non-mutexed field
• Also nil pointer deref should happen as the pointers susceptible of being nil are checked

Gotta work on :

• Clarifying timeserie flow
• Refactor timeserie code
  • Do it well
• Create an alerting decision engine based on config.*Threshold values (good idea?)