Zabbix agent2 for multiple Oracle instances on the server

[nivethaa]

I have set up LLD rule with host prototype and Oracle template linked with {$ORACLE.SERVICE} macro overridden with the SIDs. It automatically created the hosts with each host representing one Oracle instance . I'm using zabbix agent active on every template, LLD, items and have one agent installed on the actual host having the oracle database .

The issue is the discovered hosts I set up through LLD all report as "the interface being down" . Should I have multiple agents running on the server with different ports for this ? or does this set up work with odbc better ?

Plz suggest .

[nivethaa]

Could somebody please suggest solutions . The discovered hosts inherit the interface and port of the parent host . The parent host is assigned a template which has the custom discovery rule to discover the services on the server and host prototype set with oracle template linked . Every host discovered is a service running . The issue is except for the parent host , all other discovered hosts shows interface unknown as it inherited from the the parent host . Hence no database data is being pulled by Zabbix .

[cyber]

I have absolutely no experience with oracle templates .. .But.. maybe you can create a discovery, which finds all instances and their data and creates hosts per instance (from prototype), which has that oracle template attached (and macros filled by discovery) and then it monitors it..

[nivethaa]

I did the same thing which you mentioned . This is not about oracle templates , this is more about the "interface being down" as there are discovered hosts per instance ( from protoype ) that inherit the same interface and port ( I have one zabbix agent on the server ) . is there somethin that I should fix in the conf file on the server or set up custom interfaces ?

[cyber]

As long as I see, it should be OK to have same agent and port there.. as it is still same host, all those instances are still monitored via the same agent... just those instance parameters (connection string macro) should be set by disco. As I see it defaults to "tcp://localhost:1521" but as I understand you need differnt port for each?
as I said, not familiar with it.. just trying to refelct some ideas... Sometimes a blind chicken also finds a worm..

[nivethaa]

That's how I set it up to use the same agent , port 10050 , just changing the connection string through discovery . The default is "tcp://localhost:1521" for all the instances , Just the connection string would change and I have set that . The host are discovered but other than the main host where the discovery rules are set , the discovered hosts does not pull DB information as it shows "Interface unknown" . I also tried to clone the host ( using the same ip and port number ) , the cloned host has the same issue too "interface unknown" . I pointed the "Hostname=" parameter to cloned host . What else can I change for the cloned host to work .