Request for adding a native way to detect and react to host enabled/disabled state changes, especially for hosts created by host prototypes and later disabled because they are no longer discovered by LLD.
In customer's environment, temporary API restrictions, source-system inconsistencies, or RMA/replacement scenarios can cause previously discovered hosts to disappear from LLD results. Customer currently uses the “disable if no longer discovered” behaviour with a 7-day period to avoid noise from temporary issues.
The current limitation is that when the host is finally disabled, there is no direct native way to create a trigger, action, or notification based on this state change. The only workaround is monitoring the audit log, which is indirect and not suitable for clean passive alerting.
Requested improvements could include:

• an actionable event when a host is enabled/disabled,
• a triggerable internal host status flag,
• a macro such as {HOST.STATUS}

  in action/media type context,

• ideally a reason field indicating whether the host was disabled manually, via API, or because it was no longer discovered by LLD.
  This would allow users to build reliable alerting and automation around discovery-related host disablement.