https://community.splunk.com/t5/Getting-Data-In/How-do-I-ingest-logs-that-have-two-dots-in-their-name/m-p/482734#M82704 <P>look here:<BR /> <A href="https://docs.splunk.com/Documentation/Splunk/8.0.3/Data/Specifyinputpathswithwildcards">https://docs.splunk.com/Documentation/Splunk/8.0.3/Data/Specifyinputpathswithwildcards</A></P> <P><CODE>*.*.log</CODE> should work on your monitor stanza</P> Fri, 24 Apr 2020 13:33:59 GMT adonio 2020-04-24T13:33:59Z https://community.splunk.com/t5/Getting-Data-In/How-do-I-ingest-logs-that-have-two-dots-in-their-name/m-p/482733#M82703 <P>I have a new client that has files named as follows: xxxx.xxxx.log Splunk is not ingesting them. How can I ingest logs that have that type of naming convention. I believe splunk is only looking at the xxx.xxx and can't match it to the /*.log stanza I have in the inputs.conf. </P> Fri, 24 Apr 2020 13:03:39 GMT https://community.splunk.com/t5/Getting-Data-In/How-do-I-ingest-logs-that-have-two-dots-in-their-name/m-p/482733#M82703 nls7010 2020-04-24T13:03:39Z https://community.splunk.com/t5/Getting-Data-In/How-do-I-ingest-logs-that-have-two-dots-in-their-name/m-p/482734#M82704 <P>look here:<BR /> <A href="https://docs.splunk.com/Documentation/Splunk/8.0.3/Data/Specifyinputpathswithwildcards">https://docs.splunk.com/Documentation/Splunk/8.0.3/Data/Specifyinputpathswithwildcards</A></P> <P><CODE>*.*.log</CODE> should work on your monitor stanza</P> Fri, 24 Apr 2020 13:33:59 GMT https://community.splunk.com/t5/Getting-Data-In/How-do-I-ingest-logs-that-have-two-dots-in-their-name/m-p/482734#M82704 adonio 2020-04-24T13:33:59Z https://community.splunk.com/t5/Getting-Data-In/How-do-I-ingest-logs-that-have-two-dots-in-their-name/m-p/482735#M82705 <P>I did put <EM>.</EM>.log, but it still doesn't seem to be picking up the files. </P> Fri, 24 Apr 2020 13:37:24 GMT https://community.splunk.com/t5/Getting-Data-In/How-do-I-ingest-logs-that-have-two-dots-in-their-name/m-p/482735#M82705 nls7010 2020-04-24T13:37:24Z