Search code examples
kubernetesdashboardhystrixetcdturbine

Discovery of Hystrix endpoints in Kubernetes (etcd)?

We're migrating to Kubernetes and many of our services are using Hystrix which expose a stream of server sent event data consumed by Turbine and visualized by a Hystrix Dashboard. I'd like to implement a service discovery plugin to Turbine which auto discovers our Hystix streams running on Kubernetes.

  1. Would it be a good idea to use labels for this? I.e. define a label that includes the path to the hystrix stream for each pod using Hystrix?
  2. If labels are not a good idea, what would be?
Solution

  • I had the same problem and I created a little project to address it. essentially I implemented a hystric instance discovery class to work with kubernetes services. You can find my project here.

    This projects is in its infancy so bugs are likely. Feedback it welcome.

    Thanks Raffaele