Monitoring multiple servers/paths with a single inputs.conf app

joesrepsolc — Fri, 26 Jul 2019 22:10:25 GMT

Trying to setup an "intelligent" inputs.conf that uses the system name of the forwarder then uses the correct path for the monitor input line based on that system name. For instance, "testserver1" uses the inputs for the directory with "server1", and "testserver2" uses the inputs for the directory with "server2".

Otherwise I have to create many separate apps, and server classes to be deployed to each individual server. There are many. Would be great to deploy 1 ap/server class to all (70) servers, and have them detect which monitor lines to use.

Can an inputs.conf be aware of the forwarders hostname, and be written to look for just that match?

testserver1.domain.com
/opt/projects/teams/server1/*.log
/opt/projects/teams/server1/webapps/access*.log*

testserver2.domain.com
/opt/projects/teams/server2/*.log
/opt/projects/teams/server2/webapps/access*.log

testserver3.domain.com
/opt/projects/teams/server3/*.log
/opt/projects/teams/server3/webapps/access*.log

Re: Monitoring multiple servers/paths with a single inputs.conf app

woodcock — Fri, 26 Jul 2019 22:47:13 GMT

The closest that you can do is this:

 /opt/projects/teams/*/*.log
 /opt/projects/teams/*/webapps/access*.log*

Re: Monitoring multiple servers/paths with a single inputs.conf app

gcusello — Sat, 27 Jul 2019 14:48:33 GMT

Hi joesrepsolc,
did you tried a single stanza with with something like this:

[monitor:///opt/projects/teams/*/]
whitelist = \.log$|webapps\/access.\.log

Bye.
Giuseppe

topic Monitoring multiple servers/paths with a single inputs.conf app in Getting Data In

Monitoring multiple servers/paths with a single inputs.conf app

Re: Monitoring multiple servers/paths with a single inputs.conf app

Re: Monitoring multiple servers/paths with a single inputs.conf app