Hello, $subj.

Previously agent.ping was working in any conditions of the host, and nodata() function was working correctly. Quote from 2.4.7 what's new:

Zabbix now tries to differentiate item timeouts from host timeouts. If another item check was successful between two failed checks of a problematic item, then the problematic item is marked as not supported after the second failed check without affecting host availability.

After upgrading to 2.4.7 I've noticed in part of the cases agent.ping check was disabled due to this improvement and agent.ping.nodata() trigger didn't work at all. Here is fixed check what I expect to work in 100% of cases:

{Template_Zabbix_Agent:zabbix[host,agent,available].max({$NODATA_AGENT})}<>1

If agent.ping is no longer reliable, documentation and official [Template App Zabbix Agent](https://www.zabbix.org/mw/images/e/e7/Template_App_Zabbix_Agent-2.2.0.xml) should be updated.