Ability to send messages to the execution log from Java #477
Labels
Milestone
Comments
7 tasks
|
Thanks |
bertfrees
added a commit
to daisy/pipeline-framework
that referenced
this issue
Jun 6, 2016
using a custom Logback appender that sents log messages to the EventBus. Attaching the right job ID is done using the same MDC based principle that was already used in IgnoreSiftAppender. This fixes issue daisy/pipeline#477 Note that this also follows the proposal of unifying the two types of messages (execution log and detailed log) through one and the same mechanism, except that XProc/XSLT messages are still sent directly to the EventBus: see issue daisy/pipeline#478. In order to support messages belonging to one job coming from several sources, the message sequence numbers are now computed automatically within MessageBuilder, and the withSequence method has been removed.
8 tasks
bertfrees
added a commit
to sbsdev/pipeline
that referenced
this issue
Mar 30, 2017
using a custom Logback appender that sents log messages to the EventBus. Attaching the right job ID is done using the same MDC based principle that was already used in IgnoreSiftAppender. This fixes issue daisy/pipeline#477 Note that this also follows the proposal of unifying the two types of messages (execution log and detailed log) through one and the same mechanism, except that XProc/XSLT messages are still sent directly to the EventBus: see issue daisy/pipeline#478. In order to support messages belonging to one job coming from several sources, the message sequence numbers are now computed automatically within MessageBuilder, and the withSequence method has been removed.
bertfrees
added a commit
to daisy/pipeline-framework
that referenced
this issue
Apr 11, 2017
using a custom Logback appender that sents log messages to the EventBus. Attaching the right job ID is done using the same MDC based principle that was already used in IgnoreSiftAppender. This fixes issue daisy/pipeline#477 Note that this also follows the proposal of unifying the two types of messages (execution log and detailed log) through one and the same mechanism, except that XProc/XSLT messages are still sent directly to the EventBus: see issue daisy/pipeline#478. In order to support messages belonging to one job coming from several sources, the message sequence numbers are now computed automatically within MessageBuilder, and the withSequence method has been removed.
bertfrees
added a commit
to daisy/pipeline-framework
that referenced
this issue
Jul 31, 2017
using a custom Logback appender that sents log messages to the EventBus. Attaching the right job ID is done using the same MDC based principle that was already used in IgnoreSiftAppender. This fixes issue daisy/pipeline#477 Note that this also follows the proposal of unifying the two types of messages (execution log and detailed log) through one and the same mechanism, except that XProc/XSLT messages are still sent directly to the EventBus: see issue daisy/pipeline#478. In order to support messages belonging to one job coming from several sources, the message sequence numbers are now computed automatically within MessageBuilder, and the withSequence method has been removed.
bertfrees
added a commit
to daisy/pipeline-framework
that referenced
this issue
Jan 8, 2018
using a custom Logback appender that sents log messages to the EventBus. Attaching the right job ID is done using the same MDC based principle that was already used in IgnoreSiftAppender. This fixes issue daisy/pipeline#477 Note that this also follows the proposal of unifying the two types of messages (execution log and detailed log) through one and the same mechanism, except that XProc/XSLT messages are still sent directly to the EventBus: see issue daisy/pipeline#478. In order to support messages belonging to one job coming from several sources, the message sequence numbers are now computed automatically within MessageBuilder, and the withSequence method has been removed.
bertfrees
added a commit
to daisy/pipeline-framework
that referenced
this issue
Jan 9, 2018
using a custom Logback appender that sents log messages to the EventBus. Attaching the right job ID is done using the same MDC based principle that was already used in IgnoreSiftAppender. This fixes issue daisy/pipeline#477 Note that this also follows the proposal of unifying the two types of messages (execution log and detailed log) through one and the same mechanism, except that XProc/XSLT messages are still sent directly to the EventBus: see issue daisy/pipeline#478. In order to support messages belonging to one job coming from several sources, the message sequence numbers are now computed automatically within MessageBuilder, and the withSequence method has been removed.
bertfrees
added a commit
to daisy/pipeline-framework
that referenced
this issue
Jul 5, 2018
using a custom Logback appender that sents log messages to the EventBus. Attaching the right job ID is done using the same MDC based principle that was already used in IgnoreSiftAppender. This fixes issue daisy/pipeline#477 Note that this also follows the proposal of unifying the two types of messages (execution log and detailed log) through one and the same mechanism, except that XProc/XSLT messages are still sent directly to the EventBus: see issue daisy/pipeline#478. In order to support messages belonging to one job coming from several sources, the message sequence numbers are now computed automatically within MessageBuilder, and the withSequence method has been removed.
|
Was fixed by daisy/pipeline-framework#127 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(didn't find an issue for this already so I'm creating this one)
The text was updated successfully, but these errors were encountered: