[ZBXNEXT-2436] New data storage method Created: 2014 Sep 04 Updated: 2014 Sep 05 Resolved: 2014 Sep 05 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Change Request | Priority: | Trivial |
Reporter: | Jacek | Assignee: | Unassigned |
Resolution: | Duplicate | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
Description |
Quite often there are parameteres that don't change their value frequently (errors on interfaces, some hardware info, temperature etc.), for which it'd be good to have a whole history of these changes, but keeping all repetitive data seems to be unnecessary.
For example, if we've received values: '0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1', in database there would be only '0 0 1', where timestamps would be:first '0' - timestamp of occurance, second '0' - timestamp of occurance of '1' decreased a little bit, '1' - timestamp of occurance. Clonning of repetitive value would simulate the actual trend of a value on graphs (like this trend would look with all data gathered). That would propably increase CPU usage for comparison process, but it would make database smaller and easier to handle. At least, I think it would . That also would allow to store detailed histroy much longer. For example, I had some problems on interface in April and in August, in other months there weren't any problems. I'm able to see exact situations from the past not only avg,mix,min from one hour period, while keeping history table as small as possible, because not storing '0-es' from other months. |
Comments |
Comment by Marc [ 2014 Sep 04 ] |
Reminds me of ZBXNEXT-2165 (incl. richlv's comment) |
Comment by Aleksandrs Saveljevs [ 2014 Sep 04 ] |
Sorry for closing. This issue talks about internal storage, the other issue talks about API output. |
Comment by richlv [ 2014 Sep 05 ] |
closing as a duplicate of |