• ZBXNEXT-1925 asks for a "dummy" interface
• ZBXNEXT-2156 asks for an ability to add hosts without interfaces

Actually, there is a functionality improvement to be found here. Consider this map:

Now, on Kaylee, I have defined web checks against Cloudflare, Comcast, Facebook, Google and Microsoft. In truth, those checks are meant to represent connectivity tests between _gateway and the public Internet, but defined on kaylee, they look like checks against my internal network.

I could attach the checks to _gateway, but then it looks like a problem with my router, and not a problem somewhere between my router and upstream.

Ideally, I'd want to be able to stick these vague "check upstream" checks on hosts that I have no control over, so there'd be no interfaces.

Also, combined with a couple subsequent features, something like this could be used to represent, e.g. wifi clients that roam from AP to AP. Combine a "generic" interface capability with the ability for LLD items to feed data to some other host, and you track client connectivity data you can only grab from individual APs and associate it with the items on a roaming host. This could also be useful for contiguously tracking VM data where VMs were vmotioned from one Vcenter to another.

I believe we can close it now, Zabbix 5.4 made host interfaces optional.

This doesn't address the Request... I believe the requester made quite a good job to describe the wanted feature.

What is desired is to be able to have a Generic Interface that is not related to SNMP, Agent or anything.

The goal is to be able to use the simple checks or scripts without the need to either define an interface that doesn't match what the device is capable of.

For instance: take a device that is only accessible through an HTTP API. You wish to create some items to fetch some metrics.

How would you do that ? It doesn't have SNMP, nor a Zabbix Agent or IPMI... You just want to be able to define the IP or FQDN of the host without having a "false" interface.

A workaround to do this is to just define some Macros containing the IP. This works for custom templates but makes you unable to re-use other Templates using simple checks, like the ICMP Template.

Another workaround is to define an interface either SNMP or Zabbix Agent that does NOT correspond to the reality.

Having a Generic interface to be able to specify the IP/FQDN only would be a huge plus in streamlining the hosts that do not communicate through a current defined protocol.

If you could reconsider your fix and re-open this feature request, that would be really considered.

Agreed. Removing ZBX interface leaves IP/DNS column in hosts table empty.

This makes it harder to understand what host is broken both in Hosts and in Trigger Action notifications.

A generic interface, would be nice way to set this IP/DNS column for inventory purposes.

Looks like ZBXNEXT-4660 is only generic interface ticket left open.