Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roadmap/direction of hystrix-dashboard #1033

Closed
mattrjacobs opened this issue Dec 31, 2015 · 3 comments
Closed

Roadmap/direction of hystrix-dashboard #1033

mattrjacobs opened this issue Dec 31, 2015 · 3 comments

Comments

@mattrjacobs
Copy link
Contributor

Internally at Netflix, we've stopped using the Hystrix dashboard. We've been using other visualization approaches, as described here: http://techblog.netflix.com/2014/01/improving-netflixs-operational.html.

We recognize that the dashboard is still relied on by many organizations and individuals, so we'd like to see it continue. However, it doesn't make sense for me personally, or Netflix as a whole, to be driving its development anymore.

My current thinking is as follows:

  • When possible (maybe ~1 month), split off the dashboard into a separate repo. In this repo, document the fact that feature development is no longer ongoing by me or anyone at Netflix.
  • I'll keep admin rights so that I may merge feature requests/bugfixes by others.
  • If someone would like to take over as maintainer of the project, I can grant admin rights and then help get all of the documentation/procedures in place so that I can handoff the project and roadmap.

I'd love input on all of the above, and am happy to answer any questions as well.

@the4yeast
Copy link

@mattrjacobs has Netflix open-sourced any of the tools they used to replace the dashboard?

@mattrjacobs
Copy link
Contributor Author

@the4yeast As of today, no. That may change as the tools get more mature.

@the4yeast
Copy link

Thanks @mattrjacobs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants