Just think about this as a pipeline that can:

1) deliver messages
2) fork to different paths and never join again (=> channel / log statement)
3) fork to different paths and then be joined again (=> junction)
4) at every fork, the message is cloned.

```

        +-- channel1 ---- destination
       /
src---+
       \                  /----\
        +-- channel 2----+      +----   destination
                          \----/
                         junction
```

On Sat, May 18, 2019 at 11:34 PM Fabien Wernli <wernli@in2p3.fr> wrote:
On Fri, May 17, 2019 at 01:19:07PM +0000, Faine, Mark R. (MSFC-IS40)[NICS] wrote:
> Thanks, that does help and I am putting in a fallback log path as the last log path.  I think junction/channel is very difficult to understand.  If/else is probably the easiest, log paths aren’t that bad, but junction/channel is very unintuitive to me.

Channels are like individual if (without else) statements.
Junctions are channel containers, all channels being connected downstream.

______________________________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
FAQ: http://www.balabit.com/wiki/syslog-ng-faq