These two terms can cause some confusion, but their understanding is crucial for small and medium environments.
History
All collected data, doesn’t matter what type, will be stored on history tables.
Trends
Trends basically are the collected data (only numeric) consolidated by hour. Zabbix Server hourly takes all values from history tables and calculates minimum, average and maximum for one hour period.
Note: string items, like character, log and text, doesn’t have trends
Housekeeper
Both data still remains on database until Housekeeper from Zabbix Server deletes it based on Keep history and Keep trends configurations:
So if you have an item with 60 seconds Update interval and 7 days for Keep history it will generates (60*24*7) 10080 rows per-item on history table.
For trend table, with 730 days configuration, it will generates (730*24*7) 17520 rows per-item.
Database tables for history/trends and theirs item type:
If you have a large environment, I recommend you to disable housekeeping, the explanation in this post.
Recommendations
“For trend table, with 730 days configuration, it will generates (24*7) 17520 rows per-item.”
should read
“For trend table, with 730 days configuration, it will generates (730*24*7) 17520 rows per-item.”
😉
After 2am simple numbers could be more complex 🙂 Thank you
Ricardo,
You use Zabbix to storage charts (interface/ traffic, for example) of servers, firewalls for 1 year? It’s recommended? Will slow the system?
thanks,
Today I only keep it for 6 months. You need to keep only the trend values for 1 year, not history, and your tables must be partitioned.
Thanks,
Actually I’m using version 2.0, so I can not do the partitioning of tables.
Paulo,
Create a partitioning procedure for 2.0 is in my backlog. sorry for while.
ps: saudações brasileiras! (brazilian stuff)
Good news about 2.0 job!
Meu ambiente não é tão monstruoso como o seu da Locaweb mas deve chegar a uns 350 devices.
Saudações, Abraços!