zabbix currently has four separate action types :

• trigger
• network discovery
• active agent auto-registration
• internal

this sort of makes sense from the technical point of view, but makes it harder for users (they have to switch between the types), and limits the functionality per the implemented type (for example, internal actions didn't get the maintenance status support - ZBXNEXT-2141).

additionally, auto-registered hosts can not be removed - host removal operation is only available for network discovery actions.

from the configuration maintenance point of view, it is very cumbersome, too. if zabbix instance has a couple of actions, it's relatively easy to recreate them for the internal events. if there are dozens... no. users resort to custom scripts to go to the database and just completely skip the internal events/actions.

the suggestion is to merge all actions, allowing all conditions and operations. there would have to be some sanity checks/decisions - what if somebody sets only auto-reg condition and then only adds "delete host" operation ?

nevertheless, that should significantly simplify some configuration tasks (like reacting to internal events in installations, having more than a few actions) and resolve several feature requests (including deletion of auto-registered hosts).