Monitoring allows administrator to create monitors, and the periodic created batches.

• A monitor is an entity like a cron, that will run periodically and copy data from a source model to a destination one.
• Every time a monitor runs it creates a batch. It stores a number of records copied from source model into the destination model.
• Administrators can then use graph view or dashboards on destination model to see the evolution of his data.

Administrators should create the destination models to store data, although you can use an existent one.

• The monitor will copy data from source model fields, into destination model fields. The destination model fields should be named with a prefix x_, for example, 'x_name' to get the 'name' field from source model.
• Administrator can also create function fields, these will be calculated every time the monitor runs.
• Administrator can use one destination model for many monitors, each monitor identifies his batches, so you can monitor same fields with different periods, and store the data in same model.
• For example one can create a monitor model for crm_lead, with field x_stage_id, to be executed every hour, and another one that will run every day. The data will be in same model, but you can filter and get the one you need, the hourly or daily. This way you will be able to see a graph with the opportunities stage evolution every hour or day.

• Release 1.2.2
  04/06/2020
  Fix bug in domain validation
• Release 1.2.1
  22/02/2020
  Fix bug in cron sincronization
• Release 1.2.0
  20/02/2020
  Enhancement, allow many monitors to store data in same destination model
• Release 1.1.1
  15/01/2020
  Bug fixing in batch generation
• Release 1.1.0
  15/01/2020
  Improved batch management
• Release 1.0.0
  17/12/2019
  Initial version