You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am opening this issue to submit a PR for moving away with turbine's pull model for aggregating metrices since it is not suitable in terms of distributed containers, where each microservice is running in different self sufficient containers and ips/ports are assigned dynamically (since in turbine we need to define host port in advance to aggregate streams).
Idea and solution I am using (Pull Model):
Create a custom jar which tap the hystrix metrics data as soon as call is made via hystrix then pushes that data into a facade (publisher). For accessing this data we have different subscribers viz: Rabbit MQ, Kafka, Spring XD, SQS or default medium (based on subscribers choice, how they wanna persist and use it. In our use case after publishing it to Kafka we persist in DB in order to create dashboards using Kibana).
Please let me know your thoughts on this. If we are good then I can go ahead and submit a PR on this.
The text was updated successfully, but these errors were encountered:
mukteshkrmishra
changed the title
Problems with turbine: Our own model for metrics tapping
Problems with turbine (Pull Model not suitable for containers): Our own model for metrics tapping (Push model)
Oct 26, 2016
@mukteshkrmishra Apologies for the delay. If I'm understanding correctly, you're trying to create a new method of getting metrics off of the instance producing Hystrix metrics that's not SSE. I agree that this seems like something interesting to pursue.
One piece of prior work we experimented with (but didn't quite finalize) was around pushing metrics over ReactiveSocket. You can see that code here: #1236. ReactiveSocket is not strictly request-reply, so we've got more options than SSE. We ended up getting rid of it temporarily since it is Java8-only and complicated the build process. I have an open issue (#1325) to get this building again.
Let me know if that work is at all interesting. If so, I can prioritize the work to get it back into master and save some effort on your part.
Hi @mattrjacobs @spencergibb ,
I am opening this issue to submit a PR for moving away with turbine's pull model for aggregating metrices since it is not suitable in terms of distributed containers, where each microservice is running in different self sufficient containers and ips/ports are assigned dynamically (since in turbine we need to define host port in advance to aggregate streams).
Idea and solution I am using (Pull Model):
Create a custom jar which tap the hystrix metrics data as soon as call is made via hystrix then pushes that data into a facade (publisher). For accessing this data we have different subscribers viz: Rabbit MQ, Kafka, Spring XD, SQS or default medium (based on subscribers choice, how they wanna persist and use it. In our use case after publishing it to Kafka we persist in DB in order to create dashboards using Kibana).
Please let me know your thoughts on this. If we are good then I can go ahead and submit a PR on this.
The text was updated successfully, but these errors were encountered: