4 ms·
Hey all. I'm one of the designer/engineers responsible for the new metrics tab. I wasn't part of the selection process regarding Ember, which is the framework
by idan 12y ago
Hey all. I'm one of the designer/engineers responsible for the new metrics tab.
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.
- grosskur 12y agoNice work. Are the metrics collected using lumbermill? https://github.com/heroku/lumbermill https://github.com/heroku/lumbermill
- idan 12y agoYes! I hope we'll have a engineering blog post covering our metrics pipeline soon.
- ollysb 12y agoOut of curiosity are they using ember-cli? (which has even stronger conventions)
- mariusandreiana 12y agoThanks! 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".