Splunk Search

Why are the extracted values different in the field?

agcorreia
Explorer

Hi all,
As I'm newbie and trying to figure out an issue with logs coming from a fortigate utm. I have no clue why I see different value from the raw log to the searched query.
Where exactly should I look for this difference? I've been checking field extraction, field aliases and so on but I could not find anything that would change the value. The correct one is "detected" but keep showing "blocked" and I have no idea who configure this before.
Any help would be welcome.
See the attached file.

0 Karma
1 Solution

agcorreia
Explorer

I just found out that a lookup csv file were there with different actions.
One column with the action from fortigate with some xxx_action and and other column with action and different types of actions. As soon as I changed the field from blocked at action side to detected, start to show correctly.
Thanks for the attention given.

View solution in original post

0 Karma

agcorreia
Explorer

I just found out that a lookup csv file were there with different actions.
One column with the action from fortigate with some xxx_action and and other column with action and different types of actions. As soon as I changed the field from blocked at action side to detected, start to show correctly.
Thanks for the attention given.

0 Karma
Get Updates on the Splunk Community!

Detecting Remote Code Executions With the Splunk Threat Research Team

REGISTER NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If ...

Observability | Use Synthetic Monitoring for Website Metadata Verification

If you are on Splunk Observability Cloud, you may already have Synthetic Monitoringin your observability ...

More Ways To Control Your Costs With Archived Metrics | Register for Tech Talk

Tuesday, May 14, 2024  |  11AM PT / 2PM ET Register to Attend Join us for this Tech Talk and learn how to ...