Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Trace Event Policy Processing on Devices Running Junos OS Evolved

An event policy is automatically triggered upon receipt of certain events, and thus it does not direct output to the terminal. To get information about the execution of event policies, you can review the event policy trace data.

Junos OS Evolved captures trace data for all applications on all nodes on the Routing Engine by default. Event policy tracing tracks and logs all event policy operations. You can view the collected traces for information about the processing of event policies, including the executed policies, their trigger events, the corresponding event policy actions, and any additional operations, warnings, and errors.

How to Display Trace Data for Event Policies

Junos OS Evolved stores the trace data from all nodes that is collected on the primary Routing Engine under the /var/log/traces directory. The master-eventd application handles event policy, and the event policy trace data is stored under the node.master-eventd.sequence-number subdirectories.

To view the event policy trace data, issue the show trace application master-eventd operational mode command.

You can include the terse option to display just the timestamp and message.

How to Modify Trace Settings for Event Policies

Junos OS Evolved traces event policy processing by default and traces all applications at the info level for informational messages. You can configure trace settings for specific applications at the [edit system application] hierarchy level. For example, you can specify the trace level of the application on a given node.

To modify event policy tracing operations, configure the settings under the [edit system trace application master-eventd] hierarchy level. The following example configures tracing for the master-eventd application at the notice level on node re0:

For more information about configuring trace settings, see trace.