From our other conversation, you wanted to know exactly what else to log. I would say log everything fhat requestlogger outputs as a start.
To be clear, this is all around what is logged when an exception occurs.
I am using the request logger. However, it does not log all requests. I listed above a sample of what the request log feature does not show. (Note I am saying what actual requests are filtered out completely from the RequestLogsFeature - not simply 'missing data from the request'.)
I agree with you Zoran - if I were to use SS as a complete replacement for razor views, I would need support like the above so it ends up in my models too! The way it works in MVC is really pretty slick. I am not sure if SS 'model binding' is pluggable or not, but if it was you could handle this yourself I would imagine.
Support for Amazon SQS was added in v4.0.48: https://github.com/ServiceStack/ServiceStack.Aws#sqsmqserver
Great, thanks. Can you consider handling the RPC model with this adapter (and the others)? I think that is very key.
@Demis - perhaps you should break this feature request into on feature request for each MQ option? That way you can close the Rabbit one, open new Windows Service Bus, Azure, etc?
Also, maybe I should make my RPC its own item...?
Thanks for your initial Rabbit MQ support.
I think you should support all 6 use cases of Rabbit out of the box. http://www.rabbitmq.com/getstarted.html
Specifically, the RPC scenario...a very common use case across all MQ agents. Something like this:
Example use case:
Just like we can use RPC over JSON to a service stack service, we can insert RabbitMQ in the middle and have X servers pulling out and processing messages from the queue and replying back.
Maybe add the full request information into this dashboard (like requested here http://servicestack.uservoice.com/forums/176786-feature-requests/suggestions/4688456-better-request-and-exception-logging )