, could you achieve what you
> need
> > > > with its Mapped Diagnostic Context [1]?
> > > >
> > > >
> > > > I.
> > > >
> > > > [1] https://logback.qos.ch/manual/mdc.html
> > > >
> > > >
> > >
j 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 McDo
gt;
> > 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/domains, and retrieving usage on a
>
ging 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
> > implements org.jclouds.logging.BaseLogger which only supports customising
> > the "standard"
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
> implements
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 w
