Getting Data In

where command with multiple sourcetypes

msarro
Builder

Greetings.
I am using multiple sourcetypes in a query that I am working with. If you open a search using something like this

sourcetype=SOURCE1 OR sourcetype=SOURCE2 OR sourcetype=SOURCE3

Playing around, if I try to filter anything with SOURCE1's events, all of the events from SOURCE2 and SOURCE3 get eliminated as well. For example (where AS_AS_Call_Type is an event field found only in SOURCE1):

sourcetype=SOURCE1 or sourcetype=SOURCE2 OR sourcetype=SOURCE3 AS_AS_Call_Type=network

Only events of SOURCE1 get returned. What I want is to keep all of the events from SOURCE2 and SOURCE3, along with the filtered events of SOURCE1.

How can I do this?

1 Solution

sophy
Splunk Employee
Splunk Employee

Hi!

Perhaps what you're trying to do is:

(sourcetype=SOURCE1 AS_AS_Call_Type=network) OR sourcetype=SOURCE2 OR sourcetype=SOURCE3

This will match events with "sourcetype=SOURCE1 AND AS_AS_Call_Type=network", as well as the other two sourcetypes.

Does that make sense?

View solution in original post

sophy
Splunk Employee
Splunk Employee

Hi!

Perhaps what you're trying to do is:

(sourcetype=SOURCE1 AS_AS_Call_Type=network) OR sourcetype=SOURCE2 OR sourcetype=SOURCE3

This will match events with "sourcetype=SOURCE1 AND AS_AS_Call_Type=network", as well as the other two sourcetypes.

Does that make sense?

msarro
Builder

Makes sense! The only command that seems not to be working is isnotnull(field) but I can do without that for now. Thank you!

0 Karma
Get Updates on the Splunk Community!

Accelerate Service Onboarding, Decomposition, Troubleshooting - and more with ITSI’s ...

Accelerate Service Onboarding, Decomposition, Troubleshooting - and more! Faster Time to ValueManaging and ...

New Release | Splunk Enterprise 9.3

Admins and Analyst can benefit from:  Seamlessly route data to your local file system to save on storage ...

2024 Splunk Career Impact Survey | Earn a $20 gift card for participating!

Hear ye, hear ye! The time has come again for Splunk's annual Career Impact Survey!  We need your help by ...