Splunk Search

How to use tstats where with structured data source?

yuanliu
SplunkTrust
SplunkTrust

tstats shows an error if I include a JSON field in "where" clause.  Same happens to CSV fields.  For example, if my source is like

{"host": "<hostname>", "IP": "<IP address>"}

and I do a search

 

| tstats count where IP = 10.0.0.1

 

Splunk displays "When used for 'tstats' searches, the 'WHERE' clause can contain only indexed fields. Ensure all fields in the 'WHERE' clause are indexed. Properly indexed fields should appear in fields.conf."

The problem with fields.conf is that it doesn't deal with original data structure.  With JSON, there is always a chance that regex will not properly capture a field.  With CSV, failure rate is even higher.

Is there some way to do tstats with structured sources? (I notice that despite the warning, tstats still performs OK.  But I'd rather users don't see such error message.)

Labels (1)
0 Karma
1 Solution

johnhuang
Motivator

This sounds like a good use case for datamodels.

View solution in original post

johnhuang
Motivator

This sounds like a good use case for datamodels.

richgalloway
SplunkTrust
SplunkTrust

I think that message appears because of the minor breakers in the IP address.  Try overriding that with the TERM operator.

| tstats count where TERM(IP=10.0.0.1)

 

---
If this reply helps you, Karma would be appreciated.
0 Karma

yuanliu
SplunkTrust
SplunkTrust

TERM will not be usable if multiple JSON paths have a node named IP.  With CSV, it's even harder, if at all possible, to define a TERM.  I will explore datamodel as @johnhuang suggested.

0 Karma
Get Updates on the Splunk Community!

AI for AppInspect

We’re excited to announce two new updates to AppInspect designed to save you time and make the app approval ...

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...