$ 269.49
Availability |
Odoo Online
Odoo.sh
On Premise
|
Odoo Apps Dependencies |
Discuss (mail)
|
Lines of code | 501 |
Technical Name |
tko_monitoring |
License | AGPL-3 |
Website | https://tkopen.com |
Versions | 14.0 13.0 15.0 12.0 |
Availability |
Odoo Online
Odoo.sh
On Premise
|
Odoo Apps Dependencies |
Discuss (mail)
|
Lines of code | 501 |
Technical Name |
tko_monitoring |
License | AGPL-3 |
Website | https://tkopen.com |
Versions | 14.0 13.0 15.0 12.0 |
Odoo Database Monitoring
Features
Technical application to monitor any model in your database at a predefined period.
This model will record the evolution of your data in time. For example the number of opportunities, every hour or day.
Administrator can also create KPI fields (function fields) that will be created every hour.
One will be able to create a graph of amount due per hour, or the ratio between created opportunities and closed ones per day/week, and store that information during 18 months or more.
Configuration
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.
Usage
This module has no direct visible effect on the system.
It provide utility features.
After administrator created the monitor models, user can create monitors to get data (batch records) periodically from source models into destination models.
If administrator created funcion fields (KPI) user will have in destination model the evolution of those KPI in time.
User can define a domain to filter source records to copy, or use an already created favorite filter domain.
Releases
- 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
Credits
Contributors
- Carlos Almeida <carlos.almeida@tkopen.com>
Author & Maintainers
This module is maintained at TKOpen Issues.
TKOpen is a Portuguese company specialized in customizing and extending Odoo. We develop custom solutions for your individual needs to help you focus on your strength and expertise to grow your business.
If you want to get in touch please contact us via mail (info@tkopen.com) or visit our website (https://tkopen.com).
Please log in to comment on this module