I have an issue whereby when importing certain events via DB Connect (v3.1.3), the 'Interesting Fields' are not populated despite all the events having the same format.
Here is a sample of the events -
30/11/2018 00:00:00.000 2018-11-30 00:00:00.000, DAYOFMONTH="30/11/2018", COUNT="1", STATUS="W", SOURCE="Call Centre", PRODUCTCODE="Xxxxxx"
30/11/2018 00:00:00.000 2018-11-30 00:00:00.000, DAYOFMONTH="30/11/2018", COUNT="2496", STATUS="Q", SOURCE="System Renewal", PRODUCTCODE="Xxxxxx"
30/11/2018 00:00:00.000 2018-11-30 00:00:00.000, DAYOFMONTH="30/11/2018", COUNT="264", STATUS="Q", SOURCE="Call Centre", PRODUCTCODE="Xxxxxx"
30/11/2018 00:00:00.000 2018-11-30 00:00:00.000, DAYOFMONTH="30/11/2018", COUNT="2012", STATUS="Q", SOURCE="System Renewal", PRODUCTCODE="Xxxxxx"
30/11/2018 00:00:00.000 2018-11-30 00:00:00.000, DAYOFMONTH="30/11/2018", COUNT="199", STATUS="Q", SOURCE="Call Centre", PRODUCTCODE="Xxxxxx"
Apologies, I do not have enough Karma points yet to post an image.
As can be seen, each event has DAYOFMONTH=, COUNT=, STATUS=, SOURCE= and PRODUCTCODE=, but these fields do not become 'Interesting Fields'. I have searched in Smart and Verbose formats and looked at 'All Fields' and they do not appear.
I know I create field extractions or use regex to create the fields (which is what I have done for now). I would like to know why Splunk is not populating the 'Interesting Fields' in this case as there are other db imports which do have 'Interesting Fields' automatically populated.
Thanks in anticipation.
... View more