search

iron-io / issues

For Iron.io services issue tracking. Public facing issue tracking for behind the scenes issues.
5 stars 0 forks source link

Logging for Message Queue #2

Open odeits opened 11 years ago

odeits commented 11 years ago

Ability to enabled Logging for a Message Queue that records Method Called, Args, Client Info, Timestamp

Reason: When debugging client code it is crucial to have transparency into the queue to eliminate sources of errors.

treeder commented 11 years ago

Hi @odeits , can you explain the use case a bit more?

odeits commented 11 years ago

I had a case where messages appeared to be vanishing. Without the ability to create a 'debug' logged queue it was more difficult than it could have been to track down the source of the missing messages. In my case it turned out a dev machine got access to the wrong credentials and was silently consuming messages it shouldn't have. With an ability to turn on minimal logging it would have been more evident that I had an extra machine talking to the queue. The biggest win is the ability to say for certain that messages were received and consumed thus leaving the debugging squarely the consumption code.

carimura commented 11 years ago

time to revisit.