<?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 you programmatically bump a search head? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/how-do-you-programmatically-bump-a-search-head/m-p/284977#M24012</link>
    <description>&lt;P&gt;If you capture the HTTP requests generated when you press the bump button you can get the POST headers which I think you could probably use to replicate this behaviour via curl. I personally use the Live HTTP Headers extension to do that:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://chrome.google.com/webstore/detail/live-http-headers/iaiioopjkcekapmldfgbebdclcnpgnlo?hl=en"&gt;https://chrome.google.com/webstore/detail/live-http-headers/iaiioopjkcekapmldfgbebdclcnpgnlo?hl=en&lt;/A&gt;&lt;BR /&gt;
&lt;A href="https://addons.mozilla.org/en-GB/firefox/addon/live-http-headers/"&gt;https://addons.mozilla.org/en-GB/firefox/addon/live-http-headers/&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;You could also try to run a refresh for just those components that you've changed. See this &lt;A href="https://answers.splunk.com/answers/102568/reload-transforms-conf-without-restarting-splunk.html"&gt;post&lt;/A&gt;.&lt;/P&gt;

&lt;P&gt;Hope that helps.&lt;/P&gt;</description>
    <pubDate>Wed, 06 Apr 2016 19:10:03 GMT</pubDate>
    <dc:creator>javiergn</dc:creator>
    <dc:date>2016-04-06T19:10:03Z</dc:date>
    <item>
      <title>how do you programmatically bump a search head?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/how-do-you-programmatically-bump-a-search-head/m-p/284976#M24011</link>
      <description>&lt;P&gt;Is there a Splunkish way (via curl or rest or something) to do the equivalent of clicking the bump button on the _bump page? It seems silly to write a script that has to generate the button click directly from that page.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2016 18:39:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/how-do-you-programmatically-bump-a-search-head/m-p/284976#M24011</guid>
      <dc:creator>cphair</dc:creator>
      <dc:date>2016-04-06T18:39:39Z</dc:date>
    </item>
    <item>
      <title>Re: how do you programmatically bump a search head?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/how-do-you-programmatically-bump-a-search-head/m-p/284977#M24012</link>
      <description>&lt;P&gt;If you capture the HTTP requests generated when you press the bump button you can get the POST headers which I think you could probably use to replicate this behaviour via curl. I personally use the Live HTTP Headers extension to do that:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://chrome.google.com/webstore/detail/live-http-headers/iaiioopjkcekapmldfgbebdclcnpgnlo?hl=en"&gt;https://chrome.google.com/webstore/detail/live-http-headers/iaiioopjkcekapmldfgbebdclcnpgnlo?hl=en&lt;/A&gt;&lt;BR /&gt;
&lt;A href="https://addons.mozilla.org/en-GB/firefox/addon/live-http-headers/"&gt;https://addons.mozilla.org/en-GB/firefox/addon/live-http-headers/&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;You could also try to run a refresh for just those components that you've changed. See this &lt;A href="https://answers.splunk.com/answers/102568/reload-transforms-conf-without-restarting-splunk.html"&gt;post&lt;/A&gt;.&lt;/P&gt;

&lt;P&gt;Hope that helps.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2016 19:10:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/how-do-you-programmatically-bump-a-search-head/m-p/284977#M24012</guid>
      <dc:creator>javiergn</dc:creator>
      <dc:date>2016-04-06T19:10:03Z</dc:date>
    </item>
    <item>
      <title>Re: how do you programmatically bump a search head?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/how-do-you-programmatically-bump-a-search-head/m-p/284978#M24013</link>
      <description>&lt;P&gt;This is for JS and CSS specifically, so I don't think there's an endpoint for those components. I'll see if I can hack the POSt headers.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Apr 2016 13:42:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/how-do-you-programmatically-bump-a-search-head/m-p/284978#M24013</guid>
      <dc:creator>cphair</dc:creator>
      <dc:date>2016-04-07T13:42:26Z</dc:date>
    </item>
    <item>
      <title>Re: how do you programmatically bump a search head?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/how-do-you-programmatically-bump-a-search-head/m-p/284979#M24014</link>
      <description>&lt;P&gt;I was just able to do this with Javascript in a Splunk dashboard. Here's the code if anyone would like it:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;function doBump(){
    $.ajax({
        url: '/en-US/_bump',
        type: 'GET',
        async: false,
        success: function(returneddata) { 
            let baseBump = returneddata; 
            let postValue = $(baseBump).find("input[type=hidden]").val();
            //console.log("Initial Bump Page", returneddata);
            $.ajax({
                url: '/en-US/_bump',
                type: 'POST',
                data: "splunk_form_key=" + postValue,
                async: false,
                success: function(returneddata) { 
                                       // console.log("Final Bump", returneddata); 
                                },
                error: function(xhr, textStatus, error) { 
                                       // console.error("Error Updating!", xhr, textStatus, error);
                            })
        },
        error: function(xhr, textStatus, error) { 
                           // console.error("Error Updating!", xhr, textStatus, error);
                    }
    })
}
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 05 Apr 2019 14:11:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/how-do-you-programmatically-bump-a-search-head/m-p/284979#M24014</guid>
      <dc:creator>David</dc:creator>
      <dc:date>2019-04-05T14:11:42Z</dc:date>
    </item>
    <item>
      <title>Re: how do you programmatically bump a search head?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/how-do-you-programmatically-bump-a-search-head/m-p/284980#M24015</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;i created a custom search command &lt;CODE&gt;| dobump&lt;/CODE&gt;. Feel free to test it out and give feedback.&lt;/P&gt;

&lt;P&gt;&lt;A href="https://github.com/schose/TA-dobump"&gt;https://github.com/schose/TA-dobump&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Cheers,&lt;/P&gt;

&lt;P&gt;Andreas&lt;/P&gt;</description>
      <pubDate>Wed, 02 Oct 2019 06:07:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/how-do-you-programmatically-bump-a-search-head/m-p/284980#M24015</guid>
      <dc:creator>schose</dc:creator>
      <dc:date>2019-10-02T06:07:16Z</dc:date>
    </item>
    <item>
      <title>Re: how do you programmatically bump a search head?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/how-do-you-programmatically-bump-a-search-head/m-p/284981#M24016</link>
      <description>&lt;P&gt;Nice ! Thank you&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2019 21:09:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/how-do-you-programmatically-bump-a-search-head/m-p/284981#M24016</guid>
      <dc:creator>C_HIEN</dc:creator>
      <dc:date>2019-10-30T21:09:27Z</dc:date>
    </item>
  </channel>
</rss>

