BOND May 2025 Trends – Artificial IntelligenceTrends – Artificial Intelligence (AI) May 30, 2025 Mary Meeker / Jay Simons / Daegwon Chae / Alexander Krey2 Context We set out to compile foundational foundational trends related to AI. A starting collection of several disparate datapoints turned into this beast. As soon as we updated one chart, we often had to update another – a data game of whack-a-mole… inadvertent or otherwise. Some of these are already apparent, while others seem likely based on current trends including lethal autonomous weapons…surveillance and persuasion…biased decision making… impact

all the specified recipients. Real-time export of events, values, trends Real-time export of trigger events, item values and trends in a newline- delimited JSON format is possible by specifying the new determine the maximum size of an individual export file. See also: Real-time export of events, values, trends Tag-based permissions User groups form has been completed with a new Tag filter tab that allows override item-level history/trends settings in the case when keeping history/trends is entirely disabled on the item level. In addition, if previously disabling item history/trends had to be specified by

override item-level history/trends settings in the case when keeping history/trends is entirely disabled on the item level. In addition, if previously disabling item history/trends had to be specified by around 500 bytes per value. • Housekeeper setting for trends Zabbix keeps a 1-hour max/min/avg/count set of values for each item in the table trends. The data is used for trending and long period graphs number of bytes required to keep single value, depends on database engine, normally ~90 bytes. Trends days*(items/3600)*24*3600*bytes items : number of items days : number of days to keep history

→ Hosts → Items has been renamed Clear history and trends to more accurately describe its function, which is the same as the Clear history and trends button in the item configuration form. In trigger around 500 bytes per value. • Housekeeper setting for trends Zabbix keeps a 1-hour max/min/avg/count set of values for each item in the table trends. The data is used for trending and long period graphs number of bytes required to keep single value, depends on database engine, normally ~90 bytes. Trends days*(items/3600)*24*3600*bytes items : number of items days : number of days to keep history

around 500 bytes per value. • Housekeeper setting for trends Zabbix keeps a 1-hour max/min/avg/count set of values for each item in the table trends. The data is used for trending and long period graphs number of bytes required to keep single value, depends on database engine, normally ~90 bytes. Trends days*(items/3600)*24*3600*bytes items : number of items days : number of days to keep history backend database. So, the total required disk space can be calculated as: Configuration + History + Trends + Events The disk space will NOT be used immediately after Zabbix installation. Database size will

around 500 bytes per value. • Housekeeper setting for trends Zabbix keeps a 1-hour max/min/avg/count set of values for each item in the table trends. The data is used for trending and long period graphs number of bytes required to keep single value, depends on database engine, normally ~90 bytes. Trends days*(items/3600)*24*3600*bytes items : number of items days : number of days to keep history * 100 bytes. So, the total required disk space can be calculated as: Configuration + History + Trends + Events The disk space will NOT be used immediately after Zabbix installation. Database size will

around 500 bytes per value. • Housekeeper setting for trends Zabbix keeps a 1-hour max/min/avg/count set of values for each item in the table trends. The data is used for trending and long period graphs number of bytes required to keep single value, depends on database engine, normally ~90 bytes. Trends days*(items/3600)*24*3600*bytes items : number of items days : number of days to keep history backend database. So, the total required disk space can be calculated as: Configuration + History + Trends + Events The disk space will NOT be used immediately after Zabbix installation. Database size will

to client certificate and private key files. Clearing history and trend data A Clear history and trends button has been added to the web scenario configuration form. 5.7 Optional SNMP bulk requests Bulk numeric items with disabled history (’history’ and ’trends’ set to 0), the Graph link is hidden from view in Monitoring → Latest data. If history and trends are set to ’0’ globally in Administration → General removed because of inability to distinguish possible network errors. 13.2.1 Trend cache improvements Trends of items that received no data during the first 55 minutes of the hour will be flushed to database

around 500 bytes per value. • Housekeeper setting for trends Zabbix keeps a 1-hour max/min/avg/count set of values for each item in the table trends. The data is used for trending and long period graphs number of bytes required to keep single value, depends on database engine, normally ~90 bytes. Trends days*(items/3600)*24*3600*bytes items : number of items days : number of days to keep history 100 bytes. 45 So, the total required disk space can be calculated as: Configuration + History + Trends + Events The disk space will NOT be used immediately after Zabbix installation. Database size will