<?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: Is there a REST API to remove missing forwarders? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Is-there-a-REST-API-to-remove-missing-forwarders/m-p/297618#M56323</link>
    <description>&lt;P&gt;&lt;A href="https://host:8089/services/deployment/server/clients?count=0"&gt;https://host:8089/services/deployment/server/clients?count=0&lt;/A&gt; to pull the full Universal Forwarder list. &lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/6.5.2/RESTREF/RESTdeploy"&gt;https://docs.splunk.com/Documentation/Splunk/6.5.2/RESTREF/RESTdeploy&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;deployment/server/clients/{name}&lt;/P&gt;

&lt;P&gt;&lt;A href="https://:/services/deployment/server/clients/{name}" target="test_blank"&gt;https://:/services/deployment/server/clients/{name}&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Get client information or remove a client.&lt;/P&gt;

&lt;P&gt;DELETE&lt;/P&gt;

&lt;P&gt;Remove the specified client from the deployment server registry. The next time the client "phones home" the record is re-created. &lt;/P&gt;</description>
    <pubDate>Wed, 29 Mar 2017 21:18:31 GMT</pubDate>
    <dc:creator>ppeterson</dc:creator>
    <dc:date>2017-03-29T21:18:31Z</dc:date>
    <item>
      <title>Is there a REST API to remove missing forwarders?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Is-there-a-REST-API-to-remove-missing-forwarders/m-p/297617#M56322</link>
      <description>&lt;P&gt;I have already found documentation on updating the "DMC Forwarder - Build Asset Table" with a post as referenced here:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://answers.splunk.com/answers/426211/is-there-a-rest-api-call-to-rebuild-the-forwarder.html"&gt;https://answers.splunk.com/answers/426211/is-there-a-rest-api-call-to-rebuild-the-forwarder.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;This does not actually achieve what I wish to do. We wish to automate via an API call how one rebuilds forwarder assets in Splunk. This is done in Splunk Web in the Distributed Management Console (DMC)-&amp;gt;settings-&amp;gt;Forwarder Monitoring Setup and then I can set the data collection interval and hit the button "Rebuild Forwarder Assets". I want an API call to do that. Is this possible? &lt;/P&gt;</description>
      <pubDate>Wed, 29 Mar 2017 19:18:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Is-there-a-REST-API-to-remove-missing-forwarders/m-p/297617#M56322</guid>
      <dc:creator>gthiers</dc:creator>
      <dc:date>2017-03-29T19:18:35Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a REST API to remove missing forwarders?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Is-there-a-REST-API-to-remove-missing-forwarders/m-p/297618#M56323</link>
      <description>&lt;P&gt;&lt;A href="https://host:8089/services/deployment/server/clients?count=0"&gt;https://host:8089/services/deployment/server/clients?count=0&lt;/A&gt; to pull the full Universal Forwarder list. &lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/6.5.2/RESTREF/RESTdeploy"&gt;https://docs.splunk.com/Documentation/Splunk/6.5.2/RESTREF/RESTdeploy&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;deployment/server/clients/{name}&lt;/P&gt;

&lt;P&gt;&lt;A href="https://:/services/deployment/server/clients/{name}" target="test_blank"&gt;https://:/services/deployment/server/clients/{name}&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Get client information or remove a client.&lt;/P&gt;

&lt;P&gt;DELETE&lt;/P&gt;

&lt;P&gt;Remove the specified client from the deployment server registry. The next time the client "phones home" the record is re-created. &lt;/P&gt;</description>
      <pubDate>Wed, 29 Mar 2017 21:18:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Is-there-a-REST-API-to-remove-missing-forwarders/m-p/297618#M56323</guid>
      <dc:creator>ppeterson</dc:creator>
      <dc:date>2017-03-29T21:18:31Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a REST API to remove missing forwarders?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Is-there-a-REST-API-to-remove-missing-forwarders/m-p/297619#M56324</link>
      <description>&lt;P&gt;Thanks! @ppeterson&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2017 19:12:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Is-there-a-REST-API-to-remove-missing-forwarders/m-p/297619#M56324</guid>
      <dc:creator>gthiers</dc:creator>
      <dc:date>2017-03-30T19:12:14Z</dc:date>
    </item>
    <item>
      <title>Re: Is there a REST API to remove missing forwarders?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Is-there-a-REST-API-to-remove-missing-forwarders/m-p/297620#M56325</link>
      <description>&lt;P&gt;Hi @ppeterson. After looking more into this, it turns out we don't have our deployment server set up because we use a 3rd party tool to set up splunk instances. Is there any other API call that can remove missing forwarders outside of the deployment server route? Or is there a macro that can be utilized? &lt;/P&gt;</description>
      <pubDate>Fri, 31 Mar 2017 15:34:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Is-there-a-REST-API-to-remove-missing-forwarders/m-p/297620#M56325</guid>
      <dc:creator>gthiers</dc:creator>
      <dc:date>2017-03-31T15:34:45Z</dc:date>
    </item>
  </channel>
</rss>

