1.9.3a, discovery and low-level discovery

[jhgrc]

I've successfully enabled host-discovery to a template which does low-level discovery for it's interfaces.

However there are a couple of issues:
1) For discovery I use SysName.0 oid to discover, and it is the string which is use to detect uniqueness of host (good for multiple host interfaces). Why this SysName.0 cannot be used to set Zabbix host name. I don't have reverse DNS for routers?

2) Low-level discovery does not seem to support long oid indices?

Snmpwalk: ciscoMgmt.336.1.6.1.1.54.13.78.65.84.73.79.78.65.76.45.73.78.83.84.10.84.79.45.84.83.83.45.73.84.80.0

Low-level discovery: ciscoMgmt.336.1.6.1.1.54
So index is: 13.78.65.84.73.79.78.65.76.45.73.78.83.84.10.84.79.45.84.83.83.45.73.84.80.0
Which can be divided into parts of lenght of 13 and 10 bytes -> ascii letters
len 13 => 78.65.84.73.79.78.65.76.45.73.78.83.84
len 10 => 84.79.45.84.83.83.45.73.84.80

It does something but on host's itemlist I cannot see those long indices. Is this right?

3) For low-level discovery I also miss ability to set item-name via prototype to ifDescr or ifAlias (which are also set up as a prototype to fetch those)? Same goes for prototyped graph names.

4) Graphs, why cannot I add text data to graph. I've item with 'text'-type of collection (ifAlias) and I'd include that to data legend of graph as I cannot have it as a graph name 'macro'

[jhgrc]

I think if low-level discovery prototypes would use actions to include item-prototypes to add as items. And with actions you could use more logic into adding items to host's item list.

For example if ifAdminStatus is disabled, it is no need to add other items to monitoring and to cause unnecessary load to systems.