Good! Keep us posted :)
If it works, this could be a good guest blog post in the jclouds blog. If
you are willing to write something we'd be super happy to publish that on
our site.
On Thu, Nov 22, 2018, 01:17 John McDonnell Hi,
>
> Cool, didn't see this class.
>
> Will investigate it over the n
Hi,
Cool, didn't see this class.
Will investigate it over the next few days.
Regards
John
On 2018/11/22 00:00:07, Ignasi Barrera wrote:
> Interesting.
>
> I see it supports Apache HttpClient and OkHttp, and we support both as http
> drivers.
>
> Actually, for OkHttp you can provide a custo
Interesting.
I see it supports Apache HttpClient and OkHttp, and we support both as http
drivers.
Actually, for OkHttp you can provide a custom module that binds your
own OkHttpClientSupplier
[1] implementation and you could initialize it with the logbook interceptor.
Could that be an option?
Hi Ignasi,
Thanks for the reply.
So the requirement we have is that we need to log both the requests and the
responses to both a database table but also a file. Additionally we would also
need to hide passwords in any requests (i.e. if we create an account on
CloudStack we need to supply a pa
Hi John,
Can you elaborate a bit?
If you use the SLF4j driver with Logback, could you achieve what you need
with its Mapped Diagnostic Context [1]?
I.
[1] https://logback.qos.ch/manual/mdc.html
On Wed, 21 Nov 2018 at 23:14, John McDonnell
wrote:
> Hi,
>
> I use JClouds for creating accounts
Hi,
I use JClouds for creating accounts/domains, and retrieving usage on a
CloudStack instance.
We need to produce better logging where by we can match requests and responses
in a single entry into a DB table.
>From what I can see a custom logging module wouldn't quite work as it
>implement
