Are you a member of the Splunk Community?
- Find Answers
- :
- Using Splunk
- :
- Splunk Search
- :
- Re: Using fillnull for multiple fields?
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What is the best way to use fillnull for multiple fields? What is the best way to avoid it working for only the first field?
Some examples are:
| fillnull value=NULL field1 field2 field3
| fillnull value=NULL field1 | fillnull value=NULL field2 | fillnull value=NULL field3
Thank You
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@dannyzen, I would choose the following above adding separate pipes for each fillnull. Separate pipe means entire record will be used again for the 2nd fillnull and so on. The fillnull command being a streaming command it would make sense to call in a single place.
| fillnull value=NULL field1 field2 field3
However, you can definitely test the actual performance using Job Inspector for both the compare and see the response time for yourself.
| makeresults | eval message= "Happy Splunking!!!"
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you
I will group the fields as field1 field2 field3
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If wanted to substitute values for null values in all the fields
you can specify |fillnull
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@dannyzen, I would choose the following above adding separate pipes for each fillnull. Separate pipe means entire record will be used again for the 2nd fillnull and so on. The fillnull command being a streaming command it would make sense to call in a single place.
| fillnull value=NULL field1 field2 field3
However, you can definitely test the actual performance using Job Inspector for both the compare and see the response time for yourself.
| makeresults | eval message= "Happy Splunking!!!"
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@dannyzen I have converted comment to Answer. Please accept to mark this question as answered!
| makeresults | eval message= "Happy Splunking!!!"
Building Reliable Asset and Identity Frameworks in Splunk ES
Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting
Automatic Discovery Part 3: Practical Use Cases
