Currently, the default zabbix_server.conf, zabbix_proxy.conf, and zabbix_agentd.conf include external configuration directories (e.g., Include=/etc/zabbix/zabbix_server.d/*.conf) mid-file.

This can cause parameters defined in included override files to be unintentionally overwritten by later defaults in the same config file — for example, EnableGlobalScripts=1 may be silently reset.

A common best practice is to avoid modifying the default configuration files and instead use separate .d/*.conf override files. This approach ensures that user-defined settings are preserved across version upgrades, where the default config files may be replaced or changed.

Including override files mid-file undermines this practice and makes the behavior unreliable and error-prone.

Suggestion:

• Move all Include= directives to the end of the default config files.
• Optionally, implement a mechanism to verify the effective configuration at runtime (e.g., ZBXNEXT-83), such as zabbix_server -T.