<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How Do I Make Host Tags Viewable By Everyone in Security</title>
    <link>https://community.splunk.com/t5/Security/How-Do-I-Make-Host-Tags-Viewable-By-Everyone/m-p/83897#M2784</link>
    <description>&lt;P&gt;Have you seen this topic: &lt;A href="http://splunk-base.splunk.com/answers/26585/force-tags-to-be-public-upon-creation"&gt;http://splunk-base.splunk.com/answers/26585/force-tags-to-be-public-upon-creation&lt;/A&gt; ? While the solution isn't publically posted, it sounds like there is a way to do it.&lt;/P&gt;

&lt;P&gt;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.&lt;/P&gt;</description>
    <pubDate>Wed, 21 Dec 2011 15:50:09 GMT</pubDate>
    <dc:creator>rtadams89</dc:creator>
    <dc:date>2011-12-21T15:50:09Z</dc:date>
    <item>
      <title>How Do I Make Host Tags Viewable By Everyone</title>
      <link>https://community.splunk.com/t5/Security/How-Do-I-Make-Host-Tags-Viewable-By-Everyone/m-p/83896#M2783</link>
      <description>&lt;P&gt;Per billbender's question asked back in 23 Mar...&lt;BR /&gt;
Was this feature still not added in any of the 4.2.x versions?&lt;/P&gt;</description>
      <pubDate>Thu, 29 Sep 2011 22:51:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-Do-I-Make-Host-Tags-Viewable-By-Everyone/m-p/83896#M2783</guid>
      <dc:creator>gekoner</dc:creator>
      <dc:date>2011-09-29T22:51:14Z</dc:date>
    </item>
    <item>
      <title>Re: How Do I Make Host Tags Viewable By Everyone</title>
      <link>https://community.splunk.com/t5/Security/How-Do-I-Make-Host-Tags-Viewable-By-Everyone/m-p/83897#M2784</link>
      <description>&lt;P&gt;Have you seen this topic: &lt;A href="http://splunk-base.splunk.com/answers/26585/force-tags-to-be-public-upon-creation"&gt;http://splunk-base.splunk.com/answers/26585/force-tags-to-be-public-upon-creation&lt;/A&gt; ? While the solution isn't publically posted, it sounds like there is a way to do it.&lt;/P&gt;

&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Dec 2011 15:50:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-Do-I-Make-Host-Tags-Viewable-By-Everyone/m-p/83897#M2784</guid>
      <dc:creator>rtadams89</dc:creator>
      <dc:date>2011-12-21T15:50:09Z</dc:date>
    </item>
    <item>
      <title>Re: How Do I Make Host Tags Viewable By Everyone</title>
      <link>https://community.splunk.com/t5/Security/How-Do-I-Make-Host-Tags-Viewable-By-Everyone/m-p/83898#M2785</link>
      <description>&lt;P&gt;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?&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jan 2012 16:55:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-Do-I-Make-Host-Tags-Viewable-By-Everyone/m-p/83898#M2785</guid>
      <dc:creator>gekoner</dc:creator>
      <dc:date>2012-01-18T16:55:48Z</dc:date>
    </item>
  </channel>
</rss>

