Description

When messenger:consume is running, the verbosity level determines how much logs you get. This, in a cloud environment, translates to money.

With no verbosity, you get basically nothing. Same with -v.

But, with -vv you start getting messages

1. message received
2. all the processing
3. message acknowledged

The issue is, this is either "nothing" or "a lot" (depending on what other loggers start spewing INFO messages, for example FOS Elastica starts outputting full requests / responses at this level, HTTP client will output all requests, etc). This can mean a lot of output gets collected from your workers.

Example

Ideally, we'd have a middle ground where -v produces just enough output to make sure the worker is still running, like

1. message received (optional?)
2. message acked / nacked
3. shutdown

This allows using verbosity more granularly where the developer wants to optimize log costs, while still getting a decent baseline of information.