Splunk Search

Why are the table command and dropping values?

jaxxsplunk
Explorer

Summary:

When using the table command, values are dropped if { is the first character.

 
 
index=someindex host="VVV" source=somesource earliest=-24h  action
          NOT( ACTION ="SUMMARY" OR ACTION="RESULT")
          | dedup ID
        |rename ID as "Rcrds Prcssd To Date"
          | rename EVENT_DT as "Date Time" EVENT as "API EVENT"
          |convert ctime(_time) as RunDate timeformat="%m/%d/%Y %H:%M %p"
          |table ID,RunDate,ACTION, "API EVENT"
          |SORT -ID
 
When the "API EVENT" field has a { starting value, the remaining values are dropped.
If I replace 
|table ID,RunDate,ACTION, "API EVENT"
with
|fields ID,RunDate,ACTION, "API EVENT"
I see the { and the remaining values for "API EVENT"
 
Why is the table comm, and dropping values?
Labels (1)
0 Karma

isoutamo
SplunkTrust
SplunkTrust

Hi

this sounds like a bug. Please report it to splunk support.

r. Ismo

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @jaxxsplunk,

only for your information, if you rename a field "| rename ID as "Rcrds Prcssd To Date"" the following " | sort -ID" doesn't run because the ID field isn't yet present!

Anyway, probably there's an error in "EVENT" field extraction.

We could help you, if you share a sample of your logs and the regex that you're using to extract the "EVENT" field to understand why sometimes your field extraction doesn't run.

The difference between table and fields is that table is a steaming command, instead fields is a non streming field, you can find a description of the command types at https://docs.splunk.com/Documentation/Splunk/8.2.4/Search/Typesofcommands 

Ciao.

Giuseppe

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...