With Zone.JS integration, we can follow Meteor's async execution path (in client) and identify more information which is not possible before.
As a result of that, error tracking can be improved and it can be used to capture stack traces over the async execution path.
meteor add meteorhacks:zones
// for older Meteor version
mrt add zones
That's all you've to do :)
If you've added zones into a Meteor application which is being monitored with Kadira, error tracking on client can be improved dramatically. See following error trace:
For more information, visit Kadira's error tracking docs.