Cookies op Tweakers

Tweakers maakt gebruik van cookies, onder andere om de website te analyseren, het gebruiksgemak te vergroten en advertenties te tonen. Door gebruik te maken van deze website, of door op 'Ga verder' te klikken, geef je toestemming voor het gebruik van cookies. Wil je meer informatie over cookies en hoe ze worden gebruikt, bekijk dan ons cookiebeleid.

Meer informatie

Door , , 4 reacties
Bron: Zabbix, submitter: Speedfightserv

Zabbix logo (27 pix)Versie 2.2.4 van Zabbix is uitgekomen. Met dit programma kan de status van netwerkservices, servers en andere netwerkapparatuur in de gaten gehouden worden. Op zichzelf kan het programma alleen simpele informatie weergeven, maar door het installeren van een zogeheten agent op de server kan ook gedetailleerdere info worden verkregen. Meer informatie over Zabbix kan op deze pagina worden gevonden en hier staan enkele screenshots. De changelog voor deze release ziet er als volgt uit:

Improved usability of the WEB front-end
Now all multiselects have also popup selection.

Performance improvements
Performance of the latest data, overview, events and other screen was significantly improved. Especially it affects users with enabled table partitioning. Also processing of new values became faster due to changes in the logic of the history cache.

Updated translations
  • Brazilian Portuguese
  • Italian
  • Japanese
  • Polish
  • Romanian
  • Russian
  • Slovak
  • Spanish
Complete List of Bug Fixes and Improvements included into 2.2.4:
  • [ZBX-8213] fixed possible crash when processing eventlog on Windows 2000,2003,XP
  • [ZBX-8358] fixed overview screen elements being displayed incorrectly after refreshing
  • [ZBX-8334] fixed selecting group prototypes in HostPrototype::get() using Oracle backend
  • [ZBX-8061] fixed vmware cluster functions returning notsupported despite clusters being discovered normally
  • [ZBX-8348] fixed processing of lld triggers; functions in a trigger expression could be wrongly placed
  • [ZBX-8095] fixed a bug in item queue that updated item's nextcheck but not its position in the queue
  • [ZBX-8343] fixed a bug in binary heap that could cause a slightly inconsistent ordering of elements in the queue
  • [ZBX-8325] fixed crash with Oracle when inserting large number of records
  • [ZBX-8336] fixed server crash with value cache is working in low memory mode
  • [ZBX-8327] fixed possible crash when processing Windows eventlog
  • [ZBX-8302] fixed ordering of discovery rules
  • [ZBX-8209] improved host and item name column widths on Monitoring / Latest data page
  • [ZBX-8287] truncate long text values to maximum field length before inserting into database
  • [ZBX-3163] fixed trigger evaluation order so that it takes dependencies into account
  • [ZBX-7373] improved performance of latest data and item overview pages by taking data for limited period only
  • [ZBX-8200] improved performance of Monitoring / Events page
  • [ZBX-7983] improved performance of "System status" widget
  • [ZBX-7901] improved value cache database operations when caching count based requests
  • [ZBX-8188] fixed IPMI items staying supported when sensor data becomes unavailable
  • [ZBX-8243] added log message when the reason for an item being in an unsupported state changes
  • [ZBX-8195] fixed web scenario step validation for httptest.create and httptest.update API methods
  • [ZBX-6531] fixed memory leak in filesystem discovery on AIX systems
  • [ZBX-8241] fixed duplicate display of actions in media type list
  • [ZBX-8269] fixed processing of active checks in agent
  • [ZBX-8238] fixed updating agent 'mtime' for logrt[] items; thanks to Yoshinori Komuro for patch
  • [ZBX-8143] triggers are now committed to the database individually when setting to an unknown state to avoid potential locking between the poller and history syncer
  • [ZBX-7968] fixed bug when proxy stopped sending history data if it had more than 1000 unmonitored item values in history table; thanks to Corey Shaw for identifying the issue and providing a patch
  • [ZBX-8251] fixed possible crash when trying to get item value from a failed vmware service with log level set to debug
  • [ZBX-8092] changed the way the number of active triggers is calculated in the dashboard and zabbix[triggers] item
  • [ZBX-8092] added disabled triggers to the configuration cache for correct macro expansion in notifications
  • [ZBX-8092] added disabled hosts and disabled items to the configuration cache for correct macro expansion in notifications
  • [ZBX-8230] changed maintenance status log messages from warning to debug level
  • [ZBX-7098] improved handling of log file rotation/truncation for logrt[] and log[] items
  • [ZBX-8210] fixed crash when attempting to evaluate an eventlog key for items obtained from the value cache
  • [ZBX-8219] fixed regression in ipmi checks to support on/off values for sent commands
  • [ZBX-8213] fixed library loading code on Windows to prevent potential crash condition
  • [ZBX-8223] fixed compilation of dummy module on 64-bit platforms by adding "-fPIC"
  • [ZBX-7387] changed default memory usage graph display method for operating system templates
  • [ZBX-8101] fixed exporting maps from Oracle database
  • [ZBX-8198] decreased verbosity of Windows agent with DebugLevel=4
  • [ZBX-7729] added data alignment to prevent crash on non x86 processors; thanks to Pablo Ruiz for patch
  • [ZBX-8202] fixed queue calculation for unavailable hosts which are monitored through a proxy
  • [ZBX-8152] added informative log message about optional database patches
  • [ZBX-8138] fixed ssh infostring searching and validation for ssh related items to allow information messages as per RFC4253 Section 4.2
  • [ZBX-7875] fixed wrongly reported system version for Windows 8.1 and Server 2012 R2
  • [ZBX-7766] fixed webscenario status code field validation to accept user macros
  • [ZBX-8127] fixed truncation of hostname on HP-UX machines
  • [ZBX-8181] fixed possible entering of "history syncer" process in an eternal loop when processing IT services
  • [ZBX-8176] fixed SQL errors while mass operations when using Oracle database
  • [ZBX-8158] fixed disabled hosts not shown in trigger selection popup when in configuration
  • [ZBX-7553] fixed graph not getting period when coming from screen
  • [ZBX-8075] fixed triggers/data without application not showing in overview
  • [ZBX-8111] fixed possible XSS in tables with vertical header row cells
  • [ZBX-7887] fixed calculated item becoming not found if referenced item becomes not supported
  • [ZBX-8100] fixed map mass deletion using Oracle
  • [ZBX-8148] fixed maintenance warning message on php < 5.4 versions
  • [ZBX-8108] fixed reading /proc virtual files without rewinding the file position
  • [ZBX-8115] added workaround for 64 bit integer binding not working with Oracle versions less than 11.2
  • [ZBX-8140] added net.udp.listen key to item popup
  • [ZBX-8123] fixed form fields show/hide switching in IE9
  • [ZBX-8083] fixed proxy performance query item conditions to be same as in dashboard
  • [ZBX-8021] fixed password changing for users with internal authentication
  • [ZBX-8133] fixed possible deadlock while updating host_inventory table
  • [ZBX-8104] fixed inverted case sensitivity for regular expressions
  • [ZBX-8117] fixed possible crash of agent under Windows after asking the "system.sw.arch" item
  • [ZBX-8093] fixed incorrect plural in global script property host and user group labels
  • [ZBX-7997] fixed applications not being displayed in template item mass update form
  • [ZBX-7825] fixed saving of the history data in sequential time order on proxy side
  • [ZBX-8035] fixed proxy queue for ICMP, JMX and SNMP items being calculated incorrectly by the server
  • [ZBX-6542] added additional information in the default server configuration file about HousekeepingFrequency parameter
  • [ZBX-8077] fixed log messages about sending/receiving of the configuration data
  • [ZBX-8060] fixed server crash when calculating queue
  • [ZBX-7867] fixed graph item drag and drop when selecting multiple items
  • [ZBX-8046] fixed application toggling in Latest data page if same item belongs to several applications
  • [ZBX-7856] added workaround for Windows _wstat64() not working with symlinks
  • [ZBX-7534] fixed buffers being too small for long function parameters containing UTF-8 characters
  • [ZBX-7046] fixed get_ip_by_socket returning an empty string for IPv4 addresses when Zabbix is compiled with IPv6 support
  • [ZBX-7630] fixed monitoring event page navigation
  • [ZBX-7990] fixed marking of unavailable agents; it could cause excess utilisation of "poller" processes
  • [ZBX-7837] fixed y axis configuration in default proxy template graph
  • [ZBX-7957] improved graph Y axis min/max value validation for line and stacked graphs
  • [ZBX-8030] fixed {HOSTNAME} macro resolving
  • [ZBX-7974] fixed host group selecting using invalid node in user group rights page
  • [ZBX-7943] fixed undefined indexes in HTTP test dashboard widget when no history is found
  • [ZBX-7809] improved validation on decimal values
  • [ZBX-7809] fixed unused graph Y axis min/max fields unsetting from db
  • [ZBX-7976] fixed template "unlink and clear" leaving items attached to parent template
  • [ZBX-7545] fixed item mass update form being rendered with a delay when updating template items
  • [ZBX-7864] fixed filter by host group in "Availability reports" page

Zabbix screenshot (620 pix)

Besturingssystemen:Linux, BSD, UNIX
Licentietype:Voorwaarden (GNU/BSD/etc.)
Moderatie-faq Wijzig weergave

Reacties (4)

Ik wil het wel eens gaan proberen icm met een simpele VPS. Zeg maar 256mb memory, 10GB diskspace. Iemand daar ervaring mee? Zeg maar met echt low end hardware en een sqlite db?
Het is erg afhankelijk hoeveel agents je wilt gaan monitoren, maar ik denk dat het aan de lage kant is voor serieus gebruik. Om even te testen is het prima natuurlijk.

Als voorbeeld:
Ik monitor zelf 155 hosts met in totaal 11.393 items, voor mijn gevoel geen hele grote omgeving. Dit gebeurd op een VM (1 vCPU, 2Gb mem, storage op een low-end SAN)

De vitals op de zabbix server:
load averages: 0.73, 0.79, 0.61
Mem: 922M Active, 623M Inact, 338M Wired, 45M Cache, 213M Buf, 39M Free

De database is 37Gb in totaal (Met 7 dagen history, 365 dagen trends). De zabbix mysql instance verwerkt ongeveer 300 queries per seconde (240 update queries, de rest zijn veel selects en een beetje inserts/deletes/enz).

Verder is het wel mijn ervaring dat elk monitoring systeem een hoge 'learning curve' heeft en je totaal niet bij het handje genomen wordt hoe iets werkt (Zie Nagios zijn configuratie methode uit 1894). Dit geld ook voor Zabbix, alhoewel de web-frontend een hoop vergemakkelijkt met het configureren.
Verder is het wel mijn ervaring dat elk monitoring systeem een hoge 'learning curve' heeft en je totaal niet bij het handje genomen wordt hoe iets werkt (Zie Nagios zijn configuratie methode uit 1894). Dit geld ook voor Zabbix, alhoewel de web-frontend een hoop vergemakkelijkt met het configureren.
Onderschat dit laatste niet - ik ben een enorme fan van het Zabbix model, maar er gaat godskleretig veel werk in zitten om het zo in te stellen als jij wilt. Als je voorgekauwde templates kunt vinden voor je apparatuur, perfect, maar zo niet, dan zul je heel wat tijd hier aan gaan spenderen.
Dat is met elk pakket zo. Ik heb het afgelopen half jaar zowat fulltime met SCOM gewerkt en nog is het niet af :)

Op dit item kan niet meer gereageerd worden.

Nintendo Switch Google Pixel Sony PlayStation VR Planet Coaster Apple iPhone 7 Dishonored 2 Google Android 7.x Watch Dogs 2

© 1998 - 2016 de Persgroep Online Services B.V. Tweakers vormt samen met o.a. Autotrack en de Persgroep Online Services B.V. Hosting door True