Discovery rules for items

[dkoski]

I have developed external commands (bash scripts) to discover and report SMART stats. The script executes smartctl and greps for item codes. This generally works well for both Linux and Windows (using Cygwin and WSL). However, different manufactures and models report items with some variation. For example, SSD media wear indicators are indicated by at least two values depending on manufacturer and of course, both are unsupported with legacy hard drives. Currently, my script returns a 100 (indicating no wear) for unsupported wear indications where unsupported. I would like to either extend discovery to items, or ignore them altogether, using a return value from the script.

[Brambo]

So what is the question? Item prototype is the way to create items based on a bunch of data. That could be delivered by script (zabbix trapper as source item) etc etc.
explained in this section:https://www.zabbix.com/documentation...tem_prototypes however I expect you to find better understandable examples here in the forum

[dkoski]

Item prototypes is, indeed, how it is done. The issue is that some items (prototypes) are unsupported as indicated in my original post. I'm looking for a clean way to ignore unsupported items (prototypes) in those cases.