What is the recommended way to monitor log files that come from the same application (so will be set to the same sourcetype), but they are at different locations on different servers?
I'm using a deployment server, so would I have a separate app for each server with its specific location, or can I somehow combine these?
Unless you are certain that all servers will only write stuff to one or the other directory, I would have 2 different apps with different configurations in inputs.conf
; otherwise you may end up indexing files you meant to ignore.
You can have single app with multiple [monitor://
for different path. You can combine those as well as long as the path can be combine using wildcards OR regular expressions metacharacters, as specified here: https://docs.splunk.com/Documentation/Splunk/6.6.3/Data/Specifyinputpathswithwildcards
Please keep in mind @joshuapetitt, that multiple locations per one sourcetype
, is completely "normal" and we end up with several [monitor://
stanzas.
@joshuapetitt - your monitor stanza with splunk's own wildcards ...
or *
can solve your purpose as suggested by @somesoni2.
This seems a brilliant approach provided your application log file name is uniquely identifiable to use with *