Please document "SNMP Walk to JSON"

[vanessa]

Hi, I understnad that zabbix refuse to document things as to sell support in a really disingenuous way.

But can you please do some reasonable documentation of SNMP Walk to JSON? It's only documented vaguely where and how to use it (and then a lot of other lacking information in these context such that you must buy support), but no useufl details beyond that.

[kyus]

I don't know what you want to do, but...

To use SNMP in Zabbix you can simply create a discovery rule and create macros to store specific patterns returned in your JSON. You can use those macros to filter the results.

And, later on, you can create item prototypes using those macros aswell (to make sure all items will have unique names and keys). Take a look at the SNMPINDEX macro, i'ts pretty useful when creating items.

Another way to learn how to accomplish whatever you are trying to do is taking a look at the templates you already have in your server. For example, you can see how SNMP is used in the template "Network Generic Device SNMP".

[vanessa]

I don't know what you want to do, but...

To use SNMP in Zabbix you can simply create a discovery rule and create macros to store specific patterns returned in your JSON. You can use those macros to filter the results.

And, later on, you can create item prototypes using those macros aswell (to make sure all items will have unique names and keys). Take a look at the SNMPINDEX macro, i'ts pretty useful when creating items.

Another way to learn how to accomplish whatever you are trying to do is taking a look at the templates you already have in your server. For example, you can see how SNMP is used in the template "Network Generic Device SNMP".

It's not hard once you know how to do it. Even my cat could do it. The issue here is that some basic things are often only partly documented. The only way to get the information you need is to either BUY training or support from zabbix (cough cough.. unethical business model... cough, sorry, got something in my throat..) or do an unreasable amount of trial and error and research (you often then stumble upon other people selling zabbix support ). I say that it's unreasonable since it's not that big of a deal to document the basic stuff since Zabbix is profiting of vulenteers when it comes to its code... but darn those who submit documentation or patches that make the UI:s not require training.

Just compare the icinga documentation. They don't even have the income that Zabbix does.

All I'm saying is that it'd be more ethnical to document things. It doesn't have to mean lost proft. Rather, there's some potential for growth there instead.

[cyber]

Hi, I understnad that zabbix refuse to document things as to sell support in a really disingenuous way.

But can you please do some reasonable documentation of SNMP Walk to JSON? It's only documented vaguely where and how to use it (and then a lot of other lacking information in these context such that you must buy support), but no useufl details beyond that.

What is there to document? You do walk, preprocess it, out comes json formatted data...

Or maybe you just don't understand jsonpath functionality to extract data from that json? I don't get it also always... But I don't accuse Zabbix not having it documented... Its my stupid head, that cannot get it...
I also struggle to find anywhere in docs something about someone hinting of buying support for this or that topic... Your conspiracy theories are getting quite ridiculous already.. Can we get a proof or you just drop the subject?

[cyber]

Just compare the icinga documentation. They don't even have the income that Zabbix does.

Oh.. just one little google search gives me
According to Gartner Peer Insights, Icinga is a company with a market value of $500 million–$1 billion
That is way-way above Zabbix (IIRC valued at ~80-100M€ ) Maybe they could write better docs also when having those extra (hundreds of) millions