This feels like something obvious but I can't find it.
Say I have a host with multiple interfaces, e.g. 1.1.1.1 and 2.2.2.2. It's easy to add both of them.
But now let's say you want to write a item key to reference it, for example to do a
icmpping[{magic},,,,]
I can't find what is the {magic} to put there to say "use the second interface", for example in a template (obviously I could hard code an IP there).
The only way I have found to do this, is to build a macro for the host and define something like {$INT1} = 1.1.1.1, {$INT2} = 2.2.2.2, but that is completely aside from the secondary interface you can define on the host screen.
In fact, so far, I haven't found anything anywhere that uses that secondary interface - you can create, but what uses it? I see no sign it's polling with anything but the default one.
Am I just going blind?
Note: I found this:
(shows someone similarly confused, trying to use [HOST.IP2], which does something else)
that thread also references a closed request for documentation clarification (which clarified that [HOST.IP2] doesn't do it), but I didn't find anything about how TO do it?
Say I have a host with multiple interfaces, e.g. 1.1.1.1 and 2.2.2.2. It's easy to add both of them.
But now let's say you want to write a item key to reference it, for example to do a
icmpping[{magic},,,,]
I can't find what is the {magic} to put there to say "use the second interface", for example in a template (obviously I could hard code an IP there).
The only way I have found to do this, is to build a macro for the host and define something like {$INT1} = 1.1.1.1, {$INT2} = 2.2.2.2, but that is completely aside from the secondary interface you can define on the host screen.
In fact, so far, I haven't found anything anywhere that uses that secondary interface - you can create, but what uses it? I see no sign it's polling with anything but the default one.
Am I just going blind?
Note: I found this:
(shows someone similarly confused, trying to use [HOST.IP2], which does something else)
that thread also references a closed request for documentation clarification (which clarified that [HOST.IP2] doesn't do it), but I didn't find anything about how TO do it?
Comment