New Heroku Dashboard and Metrics now in Beta
blog.heroku.com
blog.heroku.com
I wasn't part of the selection process regarding Ember, which is the framework powering the entirety of dashboard-next. My personal feelings towards it are pretty ambivalent; as a python guy, I find it tastes a lot like ruby/rails (lots of magic). That being said, Heroku is a growing org, and a lot of people were involved in building out the new Dashboard — the strong conventions of Ember do make it easier for large teams to work together without multiple styles creeping into your codebase.
There's still a lot we'd like to do with Heroku Metrics, but we had to draw the line somewhere and ship a v1 that fulfilled a value proposition. Enjoy it, do (please!) give us feedback, and we'll iterate our way to yet more visibility into your app's behavior.
Sorry/surprised to see the Metrics feature is enabled only for applications with more than one running dyno.
My biggest question remains "When should I enable a 2nd dyno for my app?" Even better, I'd like to say to Heroku "when this app is overwhelmed, enabled at most X dyno(s), and turn them off as activity decreases".
Both have good features and "bad" features?
No framework is perfect.I'd say angularjs is to ember what springmvc is to rails.
That, and the router is amazing. Plus there's an actual focus on data, as opposed to angular's free for all
https://blog.heroku.com/archives/2014/8/5/new-dashboard-and-...
Ninefold is, from my experience, everything you'd ever want from Heroku and much more (which in turn means much less). Far more simple UI and implementation, and extremely passionate and responsive dev team.
Please try out Ninefold if you've ever said "fuck you Heroku" like I have so many times.