Hi Chris! Take a look at the documentation of LoggerResource annotation: https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/resources/LoggerResource.html You can annotate a field of ComputeTask, ComputeJob or some other classes and use the injected logger during execution.
Does it fit your requirements? Denis ср, 20 сент. 2017 г. в 21:11, Chris Berry <[email protected]>: > Hi, > > We wish to implement request tracing in our Ignite Compute Grid. > > Typically we handle all of this at the Jersey/Servlet level. > Where we pass a Header to the webapp, causing a Filter to then write a flag > into the Logger's MDC, > which, in turn, we use to tell Logback to enable TRACE logging on that > particular Thread. > > Done using Jersey's ContainerRequestFilter and ContainerResponseFilter. > And Logback's MDCFilter. > > So before I start building something on top of our ComputeTask and > ComputeJob, > is there any built-in mechanism for request tracing in Ignite?? > (there is nothing I could find) > > And is there any Filter mechanism that fits this sort of concept?? So that > I > can do this out-of-band. > (what I've found is not really a fit) > > Thanks, > -- Chris > > > > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
