![]() ![]() trapper - trapper for active checks, traps, proxy communication.close problem, acknowledge problem, check item value now, remote command functionality) task manager - process for remote execution of tasks requested by other components (e.g.self-monitoring - process for collecting internal server statistics.preprocessing worker - process for data preprocessing.preprocessing manager - manager of preprocessing tasks.poller - normal poller for passive checks.icmp pinger - poller for icmpping checks. ![]() housekeeper - process for removal of old historical data.discoverer - process for discovery of devices.configuration syncer - process for managing in-memory cache of configuration data.availability manager - process for host availability updates.See the configuration file options for details on configuring zabbix_proxy. You can only run proxy as 'root' if you modify the 'AllowRoot' parameter in the proxy configuration file accordingly. If you will try to run it as 'root', it will switch to a hardcoded 'zabbix' user, which must be present on your system. So you can run proxy as any non-root user without any issues. It will run as whatever non-root user it is started as. Zabbix proxy is designed to run as a non-root user. Increase log level of all processes: shell > zabbix_proxy -c /usr/local/etc/zabbix_nf -R log_level_increase Increase log level of second poller process: shell > zabbix_proxy -c /usr/local/etc/zabbix_nf -R log_level_increase=poller,2 Increase log level of process with PID 1234: shell > zabbix_proxy -c /usr/local/etc/zabbix_nf -R log_level_increase=1234 Decrease log level of all http poller processes: shell > zabbix_proxy -c /usr/local/etc/zabbix_nf -R log_level_decrease= "http poller" Process user Scope - rwlock, mutex, processing can be used with the process type and number (e.g., history syncer,1,processing) or all processes of type (e.g., history syncer,rwlock)Įxample of using runtime control to reload the proxy configuration cache: Process type,N - Process type and number (e.g., history syncer,1) Process type - All processes of specified type (e.g., history syncer) For larger values specify target as 'process type,N'.ĭecrease log level, affects all processes if target is not specified.Īffects all processes if target is not specified.Įnabled profiling provides details of all rwlocks/mutexes by function name. Process type,N - Process type and number (e.g., poller,3) Process type - All processes of specified type (e.g., poller) Increase log level, affects all processes if target is not specified. Ignored if the housekeeping procedure is currently in progress. Reload SNMP cache, clear the SNMP properties (engine time, engine boots, engine id, credentials) for all hosts. Locks - list of mutexes (is empty on **BSD* systems) Preprocessing - preprocessing manager statistics Gather diagnostic information in the proxy log file. Passive Zabbix proxy will request configuration data from Zabbix server the next time when the server connects to the proxy. ![]() Ignored if cache is being currently loaded.Īctive Zabbix proxy will connect to the Zabbix server and request configuration data. If override is disabled and tables have compressed chunks, the housekeeper will not remove data from these tables, and warnings about incorrect configuration will be displayed in the Housekeeping and System information sections.Īll of these parameters can be changed in Administration → Housekeeping after the installation.Reload configuration cache. ![]() To successfully remove compressed data by housekeeper, both Override item history period and Override item trend period options must be enabled. It is also possible to enable override individually either for history only or trends only.įor PostgreSQL version 10.2 or higher and TimescaleDB version 1.5 or higher, the timescaledb.sql script sets two additional parameters: In order to use partitioned housekeeping for history and trends, both these options must be enabled. The timescaledb.sql script sets the following housekeeping parameters: Zabbix server and frontend must be down for the period of migration. The migration of existing history and trend data may take a lot of time. Regardless of this warning, the configuration will be completed successfully. Please ignore warning messages informing that the best practices are not followed while running timescaledb.sql script on TimescaleDB version 2.9.0 and higher. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |