I'm sorry to use "answer question" as a way to post, but this wouldn't fit in a "comment".
So, here I am;
I did the change in transforms.conf,
I receive the logs in the right index, then,
It's not found by Splunk for Fortigate, for example in Traffic dashboard.
Let's say this :
I got 3 types of fortigate data coming into port 514. Source 1, source 2, source 3; they are separated into index1, index2, index3. Index1 and index2 are perfectly working, and Splunk for Fortigate shows their results in its dashboards. Data of index3 should be shown as well, and it isn't.
When I go in "full report" in Splunk for Fortigate, then change the search into "index=index3", it finds the data, which has the type "fortigate_traffic" by the way. When I do sourcetype="fortigate_traffic" , it shows only data from index1 and index2. If i do sourcetype="fortigate_traffic" AND index="index3", it shows the same result than index="index3".
Here is how my files look. The setnull is used because there are 2 other sources I'd like not to index, otherwise the 500 Mb/day would be blown up. The first [index3] you see is the one I just added according to the documentation I read that you headed me to.
props.conf :
[fortigate]
TRANSFORMS-fw_index = index1, index2, index3
TRANSFORMS-null = setnull
transforms.conf :
[setnull]
REGEX = [hereisaDevice_ID]|[hereisanotherDevice_ID]
DEST_KEY = queue
FORMAT = nullQueue
[index3]
FORMAT = sourcetype::fortigate
DEST_KEY = MetaData:Sourcetype
[index1]
DEST_KEY = _MetaData:Index
REGEX = [hereisanotherDevice_ID]
FORMAT = index1
[index2]
DEST_KEY = _MetaData:Index
REGEX = [yetanotherDevice_ID]
FORMAT = index2
[index3]
DEST_KEY = _MetaData:Index
REGEX = [hereisagainaDevice_ID]|[anotherDevice_IDagain]
FORMAT = index3
(There are even more things I could explain that are related to this, but it would be seriously even longer and more complicated, and I think the problem I showed here is "enough" already.) So, what am I doing wrong? I seriously don't get it.
edit : oh. Time for me to post, you posted already. Reading and trying what you said. Thanks!
... View more