Splunk Enterprise Security

Splunk ES - Troubleshooting Web Data Model

jwalzerpitt
Influencer

We have ES up and running and I'm starting to review the various Security Domains and relevant dashboards/reports.

For Security Domain -- Network -- Web Center there is a widget of 'Events Over Time By Status' that when I send to a search returns values other than HTTP status codes (200, 401, etc).

I do a pivot of the web data model and select 'status' and 'sourcetype' and I see the pan:threat sourcetype from our Palo Alto logs included with values that do not correspond to HTTP status codes.

Where would, or how would I go about excluding the pan:threat sourcetype from either the search, or from 'status' altogether?

The search is as follows:

| `tstats` count from datamodel=Web.Web where * by _time,Web.status span=10m 
| timechart minspan=10m useother=`useother` count by Web.status 
| `drop_dm_object_name("Web")`
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

I'm tempted to modify the CS to exclude the PAN events.

| `tstats` count from datamodel=Web.Web where NOT sourcetype=pan:threat by _time,Web.status span=10m 
| timechart minspan=10m useother=`useother` count by Web.status 
| `drop_dm_object_name("Web")`
---
If this reply helps you, Karma would be appreciated.

View solution in original post

0 Karma

richgalloway
SplunkTrust
SplunkTrust

I'm tempted to modify the CS to exclude the PAN events.

| `tstats` count from datamodel=Web.Web where NOT sourcetype=pan:threat by _time,Web.status span=10m 
| timechart minspan=10m useother=`useother` count by Web.status 
| `drop_dm_object_name("Web")`
---
If this reply helps you, Karma would be appreciated.
0 Karma

jwalzerpitt
Influencer

Thx Rich - worked perfectly

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...