<?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: Monitoring Circuit Breaker Status in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/Monitoring-Circuit-Breaker-Status/m-p/627893#M51474</link>
    <description>&lt;P&gt;It almost works, but as the log of the changing of the circuit breaker only comes once, the second it OPENS it is registered, but it soon drops, even though the circuit breaker stills is OPEN and still didn't receive the log of HALF-OPEN.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Stephcg_0-1674333358986.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/23488i07C56D584E727688/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Stephcg_0-1674333358986.png" alt="Stephcg_0-1674333358986.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Stephcg_0-1674333358986.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;But thank you for trying to help, I'll try a little more, or maybe, I'll just show on a table the one's who are currently open. But if I find anything, I'll report here.&lt;/P&gt;</description>
    <pubDate>Sat, 21 Jan 2023 21:27:43 GMT</pubDate>
    <dc:creator>Stephcg</dc:creator>
    <dc:date>2023-01-21T21:27:43Z</dc:date>
    <item>
      <title>Monitoring Circuit Breaker Status?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Monitoring-Circuit-Breaker-Status/m-p/627823#M51468</link>
      <description>&lt;P&gt;Hello!&lt;BR /&gt;I'm implementing a custom circuit breaker in my application spring gateway application, which returns the following event/log:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;1/20/23&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1:20:28.487 PM&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/TD&gt;
&lt;TD&gt;
&lt;DIV class=""&gt;
&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class=""&gt;[&lt;SPAN class=""&gt;app=teste-gateway&lt;/SPAN&gt;, &lt;SPAN class=""&gt;traceId=traceid&lt;/SPAN&gt;, &lt;SPAN class=""&gt;spanId=spanId&lt;/SPAN&gt;, &lt;SPAN class=""&gt;INFO&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;CircuitBreakerCustomConfig&lt;/SPAN&gt; &lt;SPAN class=""&gt;:&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;Circuit&lt;/SPAN&gt; &lt;SPAN class=""&gt;breaker&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class=""&gt;circuitBreakerName=/test-circuit-breaker-gateway-route&lt;/SPAN&gt; &lt;SPAN class=""&gt;&lt;SPAN class=""&gt;onStateTransition=State&lt;/SPAN&gt; &lt;SPAN class=""&gt;transition&lt;/SPAN&gt; &lt;SPAN class=""&gt;from&lt;/SPAN&gt; &lt;SPAN class=""&gt;CLOSED&lt;/SPAN&gt; &lt;SPAN class=""&gt;to&lt;/SPAN&gt; &lt;SPAN class=""&gt;OPEN&lt;/SPAN&gt;&lt;/SPAN&gt; &lt;SPAN class=""&gt;fromState=CLOSED&lt;/SPAN&gt; &lt;SPAN class=""&gt;toState=OPEN&lt;/SPAN&gt; &lt;SPAN class=""&gt;stateName=CLOSED_TO_OPEN&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class=""&gt;
&lt;UL class=""&gt;
&lt;LI&gt;&lt;SPAN class=""&gt;host =&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp; host-ip&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN class=""&gt;source = http:source-test&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN class=""&gt;sourcetype = sourcetype_teste-gateway&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&lt;BR /&gt;There are about 120 hosts of this application.&lt;BR /&gt;If a request to a route starts receiving many errors it will open the circuit, and it will receive the above event, and eventually until the route stabilizes it will change to HALF-OPEN and CLOSED. Each route is represented by the&amp;nbsp;&lt;SPAN class=""&gt;circuitBreakerName field.&lt;BR /&gt;So, for example, in an instance/host, the route: &lt;U&gt;&lt;EM&gt;/test-circuit-breaker-gateway-route&lt;/EM&gt;&lt;/U&gt;&amp;nbsp;will not have the above event/log until it opens the circuit due to many errors. Then it will receive the log just like the above with&amp;nbsp;stateName=CLOSED_TO_OPEN. Eventually, it will change to&amp;nbsp;stateName=OPEN_TO_HALF-OPEN, and then it can go to&amp;nbsp;stateName=HALF-OPEN_TO_OPEN (if the errors continue) or&amp;nbsp;stateName=HALF-OPEN_TO_CLOSED (if errors stop).&lt;BR /&gt;And according with how the requests are being balanced between hosts, I can have hosts where the circuit is currently HALF_OPEN, whereas at the same moment, others hosts have the circuit OPEN for the same route.&lt;BR /&gt;I would like to keep track of the routes with an OPEN circuit as it last status (most recent).&lt;BR /&gt;It could be something like a Line Chart, that Y-axis is the number of hosts with currently OPEN circuit, and X-axis is time.&lt;BR /&gt;So, I imagine that I'll have to check the last status of the above log for every host and search for OPEN. But I'm not really sure how to do this.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Is it possible? How can I do this?&lt;/P&gt;
&lt;P&gt;Thank you for any help in advance. And sorry if I wrote anything wrong, english is not my main language.&lt;/P&gt;
&lt;P&gt;&lt;SPAN class=""&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Jan 2023 15:54:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Monitoring-Circuit-Breaker-Status/m-p/627823#M51468</guid>
      <dc:creator>Stephcg</dc:creator>
      <dc:date>2023-01-23T15:54:03Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring Circuit Breaker Status</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Monitoring-Circuit-Breaker-Status/m-p/627859#M51470</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/252885"&gt;@Stephcg&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Can you please try below?&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=gateway source=http:source-test sourcetype=sourcetype_teste-gateway toState=OPEN 
| timechart dc(host) as count by circuitBreakerName&lt;/LI-CODE&gt;</description>
      <pubDate>Sat, 21 Jan 2023 02:59:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Monitoring-Circuit-Breaker-Status/m-p/627859#M51470</guid>
      <dc:creator>scelikok</dc:creator>
      <dc:date>2023-01-21T02:59:48Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring Circuit Breaker Status</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Monitoring-Circuit-Breaker-Status/m-p/627893#M51474</link>
      <description>&lt;P&gt;It almost works, but as the log of the changing of the circuit breaker only comes once, the second it OPENS it is registered, but it soon drops, even though the circuit breaker stills is OPEN and still didn't receive the log of HALF-OPEN.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Stephcg_0-1674333358986.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/23488i07C56D584E727688/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Stephcg_0-1674333358986.png" alt="Stephcg_0-1674333358986.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Stephcg_0-1674333358986.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;But thank you for trying to help, I'll try a little more, or maybe, I'll just show on a table the one's who are currently open. But if I find anything, I'll report here.&lt;/P&gt;</description>
      <pubDate>Sat, 21 Jan 2023 21:27:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Monitoring-Circuit-Breaker-Status/m-p/627893#M51474</guid>
      <dc:creator>Stephcg</dc:creator>
      <dc:date>2023-01-21T21:27:43Z</dc:date>
    </item>
  </channel>
</rss>

