Right now can get job statistics from New Relic, via using the Msgflo tool. However not everyone uses New Relic or MsgFlo. Everyone uses Heroku though, so would be nice with some generic baseline tool,
that would analyze the Heroku log of worker(s).
Would look for a (configurable) message to indicate message received, message processed successfully, message processing failed/errored.
Not that in case of concurrent processing, we'd need a unique indentifier for the message/job to be able to identify which it is.
Would be implemented similar to the guv-heroku-workerstats tool.
Should also be able to take input as a stream.
Right now can get job statistics from New Relic, via using the Msgflo tool. However not everyone uses New Relic or MsgFlo. Everyone uses Heroku though, so would be nice with some generic baseline tool, that would analyze the Heroku log of worker(s). Would look for a (configurable) message to indicate message received, message processed successfully, message processing failed/errored. Not that in case of concurrent processing, we'd need a unique indentifier for the message/job to be able to identify which it is.
Would be implemented similar to the
guv-heroku-workerstatstool. Should also be able to take input as a stream.