nathanmarz/storm — pull request #242 by velvia (2012-06-10 15:49:26+00:00)
Title: 0.8.0 more 

Add info about the taskId that is emtting, failing, or acking tuples, and the spout taskId to which ack and fail events are sent. This would be very useful for, say, a custom monitoring system implemented on top of the hooks. The taskId allows all of the events to be correlated to the local worker JVM's tasks.

I didn't see any tests for hooks.

I have other ideas for extending hooks:
- Add an event for calling execute(tuple) on a bolt task
- Add hooks for starting and cleaning up a child worker
- Add documentation :)