No, it is not possible

Yes, by using Zabbix agent or HTTP checks

If the previous preprocessing step failed, it can process and fix the error

As a first preprocessing step it catches 'not supported' messages reported by items and uses 'Custom on fail' options to process the error

As a last preprocessing step it can fix problems with incompatible value types (for example, character written to integer type)

All currently unallocated discovery workers

One discovery worker per type of check

Only one discovery worker per discovery rule

Events with matching tags accross the entire Zabbix instance

Events with matching tags created by any trigger on the same host

Events with matching tags created by the same trigger

All of these options are available for selection

JSON

Plain text

Hex-STRING

You need to change the hostname of the proxy manually in the Zabbix frontend

The Zabbix server will detect the new hostname automatically during the next hour

You need to restart the Zabbix sever to clear the cached proxy entries or issue the command 'zabbix_server -R proxy_config_cache_reload'

Timeout 5 seconds for all connections established by Agent pollers

The Zabbix server will run 5 Agent poller instances when started

Each agent poller can connect to a maximum of 5 different Zabbix agents

The Zabbix server will automatically start additional Agent pollers if required, but not more than 5

User macro

Built-in macro

Low-level discovery macro

Expression macro

Collected data are sent directly from the Zabbix proxy memory buffer. Data are saved to a database only if communication is lost between the Zabbix server and proxy

Collected data are always written to a local Zabbix proxy database before sending them to the Zabbix server

Data are never saved to a local database, only a memory buffer on Zabbix proxy is used

Only events from data collected by the same proxy group

Any events created by triggers accross entire Zabbix instance

Only events having the same tag names

Only events created by triggers on hosts in the same host group

Only events created by triggers on the same host