A source to learn the very basics of OIDs and Keys in Zabbix?

[John_W]

Coming from Solarwinds, how Zabbix handles OIDs is different and there were no Keys to work with in SW. I've read the manual and watched videos, but it appears these topics aren't covered in the detail I need.

OIDs. Technically, the OID is just the numerical listing of a given OID, but Zabbix allows action terms like walk or get and puts the OID in brackets. It looks like you can also have a list of OIDs. I think I saw one example with macros. Perhaps that was in the Key field.

Keys. It appears there are predefined keys that have names with periods separating the portions of the name but there are some that do not. Can you create your own key using either syntax? Do the keys need to match the descriptions of the OIDs?

If there is a video that goes into the basics of OIDs and Keys that goes into the real basics of these two topics, I would really like to get a link.

[cyber]

walk and get. As names suggest, one is for walking a tree and get multiple values back, other one is getting a single value. Walk can also be used for low level discovery.
This is described also in docs... https://www.zabbix.com/documentation...itemtypes/snmp

Name	Enter the item name.
Type	Select SNMP agent here.
Key	Enter the key as something meaningful.
Host interface	Make sure to select the SNMP interface, e.g. of your switch/router.
SNMP OID	Use one of the supported formats to enter OID value(s): walk[OID1,OID2,...] - retrieve a subtree of values. For example: walk[1.3.6.1.2.1.2.2.1.2,1.3.6.1.2.1.2.2.1.3].

I am not sure, what you mean with predefined keys... Can you give example? Do you mean the "legacy" way of describing SNM agent items? Described in same place as the example above is... I just copied beginning of the OID definition, but it also contains get and "legacy way" in docs...
For "SNMP agent" type items key is "something meaningful", as said ebove... For agent items (type "Zabbix agent" or "Zabbix agent (active)") you have to follow key syntax more precicely, they are hardcoded and require specific options.

The macros you saw in key field were probably LLD macros, these get filled with info from discovery, so you can create similar items all at once (for example entries for interface stats for all interfaces at once). https://www.zabbix.com/documentation...evel_discovery

[troffasky]

Example of predefined keys = what you would use with Zabbix Agent-type items, so no use for SNMP.
IMO the key field should be redundant with SNMP items, the OID pretty much is the key.

[John_W]

"For agent items (type "Zabbix agent" or "Zabbix agent (active)") you have to follow key syntax more precisely; they are hardcoded and require specific options."

Those are examples of what I called pre-defined. It is based on the Item type chosen. Not all item types have those Keys listed. If they are not listed, how do you know what information is valid to request for the Item?

[John_W]

With a simple device, like a UPS, what Key do I put in to "write something useful"? If I have a Tripp-Lite template that has the list of information I want to get for any UPS, would I have to fill out this discovery rule?