Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Admin Other
- :
- Security
- :
- How Do I Make Host Tags Viewable By Everyone
- 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
Per billbender's question asked back in 23 Mar...
Was this feature still not added in any of the 4.2.x versions?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you seen this topic: http://splunk-base.splunk.com/answers/26585/force-tags-to-be-public-upon-creation ? While the solution isn't publically posted, it sounds like there is a way to do it.
The other option I can think of would be to run a scheduled script that takes the tags.conf file from each Splunk user's directory and merges them into one tags.conf file in $SPLUNK_HOME/etc/system/local/. Optionally, the script could do some more advanced processing/filtering to only copy specific tags to the /local tags.conf. The downfall here is that Splunk needs to be restarted after the tags.conf file is changed for the changes to be seen.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you seen this topic: http://splunk-base.splunk.com/answers/26585/force-tags-to-be-public-upon-creation ? While the solution isn't publically posted, it sounds like there is a way to do it.
The other option I can think of would be to run a scheduled script that takes the tags.conf file from each Splunk user's directory and merges them into one tags.conf file in $SPLUNK_HOME/etc/system/local/. Optionally, the script could do some more advanced processing/filtering to only copy specific tags to the /local tags.conf. The downfall here is that Splunk needs to be restarted after the tags.conf file is changed for the changes to be seen.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OK, so you are saying it is still not a feature in the current version, but there are workarounds, albeit messy ones. But aren't they always?
Accelerating Observability as Code with the Splunk AI Assistant
Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...
Congratulations to the 2025-2026 SplunkTrust!
