Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Historical data
#5
Hi matthieu,

I see it now and that's a normal behaviour. The problem you see here is not because the module is not saving the historical data, but because the value doesn't change.

Due to the database behaviour design of Pandora FMS, the values are NOT saved on the database if they remain unvariable consecutively.

For example look at this scenario:

Code:
1. check 10:00 - value = 10
2. check 10:05 - value = 10
3. check 10:10 - value = 10
4. check 10:15 - value = 12
5. check 10:20 - value = 14
6. check 10:25 - value = 14
7. check 10:30 - value = 14
8. check 10:35 - value = 16

In this case, you will only see the following values:
Code:
1. check 10:00 - value = 10
2. check 10:15 - value = 12
3. check 10:20 - value = 14
4. check 10:35 - value = 16

The system knows the values in the midle did not change, so they are discarded knowing that the value will be the same untill the next different value, so the graphs can still be represented correctly. This was designed to slow down the database growing.

Kind regards,
Antonio.
 Reply
Messages In This Thread
Historical data - by matthieu.deloy - 02-08-2017, 09:00 AM
Re: Historical data - by antonio - 02-08-2017, 09:12 AM
Re: Historical data - by matthieu.deloy - 02-08-2017, 09:24 AM
Re: Historical data - by matthieu.deloy - 02-08-2017, 10:07 AM
Re: Historical data - by antonio - 02-08-2017, 03:33 PM


Users browsing this thread: 1 Guest(s)


(c) 2006-2018 Artica Soluciones Tecnol├│gicas. Contents of this wiki are under Create Common Attribution v3 licence. | pandorafms.com | pandorafms.org

Theme © MyBB Themes