https://github.com/mesos/chronos/blob/f6220eaeab55b44c32e953d0843d5042e505da2f/src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosJobFramework.scala#L91)
Anyone have luck getting chronos configured to log those messages to stdout/stderr?
--
You received this message because you are subscribed to the Google Groups "chronos-scheduler" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chronos-scheduler+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hey Craig,I don't have a useful answer to your question, but there were a bunch of breaking changes along the 3.0 branch and Mesosphere at least is recommending 2.5.1 instead :). + Gastón in case he has anything to add.Best!Judith
On Thu, Apr 19, 2018 at 5:50 AM, Craig Wickesser <code...@gmail.com> wrote:
I've been able to configure logback to get more logging from the Chaos library, but I haven't been able to get the FINE level messages that chronos logs (example:
I'm looking at chronos 3.0.0.https://github.com/mesos/chronos/blob/f6220eaeab55b44c32e953d0843d5042e505da2f/src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosJobFramework.scala#L91)
Anyone have luck getting chronos configured to log those messages to stdout/stderr?
--
You received this message because you are subscribed to the Google Groups "chronos-scheduler" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chronos-schedu...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.