Splunk Search

default visibility of extracted field

aniketb
Path Finder

I'm working on a report that uses lot of fields. I would be extracting those fields across many sourcetypes. I have my personal username in splunk. This question just struck me,

"What is the default visibility of extracted fields?"

Is is visible to all other users also? If it is, it's better that I delete the one time use extractions so as not to clutter Splunk.

0 Karma
1 Solution

lguinn2
Legend

By default, your field extractions are private, if you created them using the Manager or the Interactive Field Extractor. You can change that selectively by going to Manager -> Fields.

Still, if they are one-time-use, you might want to delete them.

And perhaps a better alternative in the future is to use the rex command, which creates field extractions on the fly. The fields created by the rex command are not saved.

View solution in original post

lguinn2
Legend

By default, your field extractions are private, if you created them using the Manager or the Interactive Field Extractor. You can change that selectively by going to Manager -> Fields.

Still, if they are one-time-use, you might want to delete them.

And perhaps a better alternative in the future is to use the rex command, which creates field extractions on the fly. The fields created by the rex command are not saved.

aniketb
Path Finder

Thanks a lot! Good description!

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...