title: Spring cloud bus - rabbitmq unavailability marks the instance DOWN
body: <p>I use spring cloud config bus (rabbitmq) in my micro-service. Only purpose for me to use rabbitmq in my microservice is spring cloud bus... I have 2 questions below.</p>
  
  <ol>
  <li><p>When I was experimenting, I found that spring expects rabbitmq to be UP and running during application start. Which is contrary to what Spring cloud evangelises... (Circuit breakers...) To be fair, even service discovery is not expected to be up and running before starting an application. Is there any sensible reason behind this...?</p></li>
  <li><p>Say, I start my application when rabbitmq is up and running. For some reason, rabbitmq goes down... What I should be losing is just my ability to work with rabbitmq... instead, /health endpoint responds back as DOWN for my micro-service. Any eureka instance listening to heart beats from my micro-service is also marking the instance as down. Any reasons for doing this...?</p></li>
  </ol>
  
  <p>To my knowledge, this is against the circuit breaker pattern that spring cloud has evangelised. </p>
  
  <p>I personally feel that spring cloud config bus is not an important feature to mark an application as down... </p>
  
  <p>Is there any alternatives to tell my spring boot micro-service that connection to rabbitmq is not a critical service? </p>
  
  <p>Thanks in advance!</p>