Click or drag to resize

Named Triggers and Loggers

Triggers and Loggers are usually anonymous, because they are directly assigned to Jobs or Checkers. This eliminates the need for them to be accessible via a LogicalName. In some use cases, however, it may make sense to use Triggers or Loggers from different Checkers or SubJobs together. You can assign such Triggers or Loggers a LogicalName and reference them via this LogicalName in other Checkers or SubJobs.

Example

Let's assume you would like to write to the shared log file from different Vishnu-nodes using the same parameters (node: generic term for all Vishnu actors). You can achieve this by giving the Logger a LogicalName and referencing it from different Vishnu-nodes. The same applies to Triggers that should start different nodes at the same time.

In the example below, the node with "Checker_1" references "FirstNamedTimerTrigger" and "FirstNamedLogger". More Checkers in the current Job or in SubJobs could do this as well. They would then listen to the same events and log with the same parameters as "Checker_1".

Named Trigger Logger
AchtungAttention

The Logger or Trigger must be defined in a separate section (see example code) in the same Job or in a higher level Job, so that it can be found by all nodes using it.