close
keyboard_arrow_left
Table of Contents
- play_arrow Overview
- play_arrow Junos Automation Scripts Overview
- play_arrow Junos XML Management Protocol and Junos XML API Overview
-
- play_arrow Automation Scripting Using XSLT
- play_arrow XSLT Overview
- play_arrow Standard XPath and XSLT Functions Used in Automation Scripts
- play_arrow Standard XSLT Elements and Attributes Used in Automation Scripts
-
- play_arrow Automation Scripting Using SLAX
- play_arrow SLAX Overview
- SLAX Overview
- SLAX Syntax Rules Overview
- SLAX Elements and Element Attributes Overview
- SLAX Elements as Function Arguments
- Understanding SLAX Default Namespaces
- XPath Expressions Overview for SLAX
- SLAX Templates Overview
- SLAX Functions Overview
- SLAX Parameters Overview
- SLAX Variables Overview
- SLAX Statements Overview
- XSLT Elements Without SLAX Equivalents
- SLAX Operators
- play_arrow SLAX Statements
- append
- apply-imports
- apply-templates
- attribute
- attribute-set
- call
- copy-node
- copy-of
- decimal-format
- element
- else
- else if
- expr
- fallback
- for
- for-each
- function
- if
- import
- key
- match
- message
- mode
- mvar
- number
- output-method
- param
- preserve-space
- priority
- processing-instruction
- result
- set
- sort
- strip-space
- template
- terminate
- trace
- uexpr
- use-attribute-sets
- var
- version
- while
- with
- play_arrow The libslax Distribution for Automation Scripting
- libslax Distribution Overview
- libslax Library and Extension Libraries Overview
- Download and Install the libslax Distribution
- libslax Default Extension Libraries: bit, curl, db, os, and xutil
- Understanding the SLAX Processor (slaxproc)
- How to Use the SLAX Processor (slaxproc)
- SLAX Debugger, Profiler, and callflow
-
- play_arrow Automation Scripting Using Python
- play_arrow Python Overview
- Understanding Python Automation Scripts for Junos Devices
- Requirements for Executing Python Automation Scripts on Junos Devices
- Overview of Python Modules on Junos Devices
- How to Use Python Interactive Mode on Devices Running Junos OS
- How to Use the psutil Module to Retrieve Process and System Information on Devices Running Junos OS
- How to Use the Requests Library for Python on Devices Running Junos OS
- IPv6 Support in Python Automation Scripts
- How to Specify the Routing Instance in Python 3 Applications on Devices Running Junos OS Evolved
-
- play_arrow Automation Script Input
- play_arrow Global Parameters in Automation Scripts
-
- play_arrow Extension Functions and Named Templates for Automation Scripts
- play_arrow Extension Functions for Automation Scripting
- play_arrow Extension Functions in the jcs and slax Namespaces
- base64-decode() Function (SLAX)
- base64-encode() Function (SLAX)
- break-lines() Function (SLAX and XSLT)
- close() Function (SLAX and XSLT)
- dampen() Function (Python, SLAX, and XSLT)
- document() Function (SLAX)
- emit_error() Function (Python)
- emit_snmp_attributes Function (Python)
- emit_warning() Function (Python)
- empty() Function (SLAX and XSLT)
- evaluate() Function (SLAX)
- execute() Function (SLAX and XSLT)
- first-of() Function (SLAX and XSLT)
- get-command() Function (SLAX)
- get-hello() Function (SLAX and XSLT)
- get-input() Function (SLAX and XSLT) and get_input() (Python)
- get-protocol() Function (SLAX and XSLT)
- get-secret() Function (SLAX and XSLT) and get_secret() (Python)
- get_snmp_action() Function (Python)
- get_snmp_oid() Function (Python)
- hostname() Function (Python, SLAX, and XSLT)
- invoke() Function (SLAX and XSLT)
- open() Function (SLAX and XSLT)
- output() Function (Python, SLAX, and XSLT)
- parse-ip() Function (SLAX and XSLT) and parse_ip() (Python)
- printf() Function (Python, SLAX, and XSLT)
- progress() Function (Python, SLAX, and XSLT)
- regex() Function (SLAX and XSLT)
- set_routing_instance() Function (Python)
- sleep() Function (SLAX and XSLT)
- split() Function (SLAX and XSLT)
- sysctl() Function (Python, SLAX, and XSLT)
- syslog() Function (Python, SLAX, and XSLT)
- trace() Function (Python, SLAX, and XSLT)
- play_arrow Named Templates for Automation Scripting
- play_arrow Named Templates in the jcs Namespace
-
- play_arrow Manage Automation Scripts
- play_arrow Store and Enable Scripts
- play_arrow Configure a Remote Source for Scripts
- play_arrow Configure the Session Protocol for Scripts
- play_arrow Control Execution of Scripts
- play_arrow Synchronize Scripts Between Routing Engines
- play_arrow Convert Scripts Between SLAX and XSLT
-
- play_arrow Commit Scripts
- play_arrow Commit Scripts Overview
- play_arrow Create and Execute Commit Scripts
- Required Boilerplate for Commit Scripts
- XML Syntax for Common Commit Script Tasks
- Design Considerations for Commit Scripts
- How to Avoid Potential Conflicts When Using Multiple Commit Scripts
- Line-by-Line Explanation of Sample Commit Scripts
- Control the Execution of Commit Scripts During Commit Operations
- Control the Execution of Commit Scripts in the QFabric System
- Configure Checksum Hashes for a Commit Script
- How to Process Large Configurations Against Commit Scripts
- Example: Retrieve the Pre-Inheritance Candidate Configuration in a Commit Script
- play_arrow Generate a Custom Warning, Error, or System Log Message Using Commit Scripts
- Overview of Generating Custom Warning, Error, and System Log Messages
- Generate a Custom Warning, Error, or System Log Message in Commit Scripts
- SLAX and XSLT Commit Script Tag Elements to Use When Generating Messages
- Example: Generate a Custom Warning Message
- Example: Generate a Custom Error Message
- Example: Generate a Custom System Log Message
- play_arrow Generate Persistent or Transient Configuration Changes Using Commit Scripts
- Overview of Generating Persistent or Transient Configuration Changes Using Commit Scripts
- Generate a Persistent or Transient Configuration Change in SLAX and XSLT Commit Scripts
- Generate a Persistent or Transient Configuration Change in Python Commit Scripts
- SLAX and XSLT Commit Script Tag Elements to Use When Generating Persistent and Transient Configuration Changes
- Remove a Persistent or Transient Configuration Change Using Commit Scripts
- Example: Generate Persistent and Transient Configuration Changes Using Commit Scripts
- play_arrow Create Custom Configuration Syntax with Commit Script Macros
- Overview of Creating Custom Configuration Syntax with Commit Script Macros
- Create Custom Configuration Syntax with Commit Script Macros
- Create a Commit Script Macro to Read the Custom Syntax and Generate Related Configuration Statements
- Example: Creating Custom Configuration Syntax with Commit Script Macros
- play_arrow Commit Script Examples
- Example: Adding a Final then accept Term to a Firewall
- Example: Adding T1 Interfaces to a RIP Group
- Example: Assign a Classifier Using a Commit Script
- Example: Automatically Configure Logical Interfaces and IP Addresses
- Example: Configure Administrative Groups for LSPs
- Example: Configure a Default Encapsulation Type
- Example: Configure Dual Routing Engines
- Example: Configure an Interior Gateway Protocol on an Interface
- Example: Control IS-IS and MPLS Interfaces
- Example: Control LDP Configuration
- Example: Create a Complex Configuration Based on a Simple Interface Configuration
- Example: Impose a Minimum MTU Setting
- Example: Limit the Number of ATM Virtual Circuits
- Example: Limit the Number of E1 Interfaces
- Example: Load a Base Configuration
- Example: Prepend a Global Policy
- Example: Prevent Import of the Full Routing Table
- Example: Require Internal Clocking on T1 Interfaces
- Example: Require and Restrict Configuration Statements
- play_arrow Junos XML and XSLT Tag Elements Used in Commit Scripts
- play_arrow Troubleshoot Commit Scripts
-
- play_arrow Op Scripts
- play_arrow Op Scripts Overview
- play_arrow Create and Execute Op Scripts
- Required Boilerplate for Op Scripts
- Map Operational Mode Commands and Output Fields to Junos XML Notation
- How to Use RPCs and Operational Mode Commands in Op Scripts
- Declare and Use Command-Line Arguments in Op Scripts
- Configure Help Text for Op Scripts
- Define Operational Mode Commands to Allow in an Op Script
- Enable an Op Script and Define a Script Alias
- Configure Checksum Hashes for an Op Script
- Execute an Op Script on the Local Device
- Execute an Op Script from a Remote Site
- Disable an Op Script
- play_arrow Op Script Examples
- Change the Configuration Using SLAX and XSLT Scripts
- Example: Change the Configuration Using SLAX and XSLT Op Scripts
- Example: Change the Configuration Using Python Op Scripts
- Example: Customize Output of the show interfaces terse Command Using an Op Script
- Example: Display DNS Hostname Information Using an Op Script
- Example: Find LSPs to Multiple Destinations Using an Op Script
- Example: Restart an FPC Using an Op Script
- Example: Export Files Using an Op Script
- Example: Import Files Using an Op Script
- Example: Search Files Using an Op Script
- play_arrow Provision Services Using Service Template Automation
- play_arrow Troubleshoot Op Scripts
-
- play_arrow SNMP Scripts
- play_arrow SNMP Scripts Overview
- play_arrow Create and Execute SNMP Scripts
- play_arrow SNMP Script Example
- play_arrow Troubleshoot SNMP Scripts
-
- play_arrow Configuration Statements and Operational Commands
list Table of Contents
keyboard_arrow_right
Trace Event Policy Processing on Devices Running Junos OS Evolved
date_range
08-Apr-25
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 by default and stores it on the Routing Engine. 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. This is different from Junos OS where you must explicitly configure traceoptions to collect event policy trace data.
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.
content_copy zoom_out_map
user@host> show trace application master-eventd 2021-06-16 13:09:47.320304999 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_33 msg = "policy should now be executed", policy = "backup_config" 2021-06-16 13:09:47.320324689 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_21 msg = "Executing Policy", policy = "backup_config" 2021-06-16 13:09:47.320348369 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_1 func_name = "eventd_policy_action_next" 2021-06-16 13:09:47.320365189 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_1 func_name = "eventd_policy_action_next" 2021-06-16 13:09:47.320372819 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_1 func_name = "eventd_policy_action_next" 2021-06-16 13:09:47.320438179 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_6 msg = "executing commands", PolicyName = "backup_config", evt_id = "UI_COMMIT_COMPLETED", cmd_file = "/tmp/evt_cmd_vfEgUQ", output_file = "/tmp/evt_op_gDnEpr" 2021-06-16 13:09:47.320464959 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_1 func_name = "eventd_substitute_variable_cmd" 2021-06-16 13:09:49.150642247 re0:master-eventd:10911:TRACE_INFO EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_38 msg = "Eventd Rcvd signal", signo = 17 2021-06-16 13:09:49.150656107 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_27 msg = "SIGCHLD received" 2021-06-16 13:09:49.150687637 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_28 msg = "SIGCHLD received", pid = 492 2021-06-16 13:09:49.150696647 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_29 msg = "Child terminated", pid = 492, status = "successfully" 2021-06-16 13:09:49.150716687 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_1 func_name = "eventd_policy_action_next" 2021-06-16 13:09:49.150735047 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_1 func_name = "eventd_upload_file" 2021-06-16 13:09:49.158191526 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_28 msg = "SIGCHLD received", pid = 0 2021-06-16 13:09:49.354883114 re0:master-eventd:10911:TRACE_INFO EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_38 msg = "Eventd Rcvd signal", signo = 17 2021-06-16 13:09:49.354901704 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_27 msg = "SIGCHLD received" 2021-06-16 13:09:49.354924204 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_28 msg = "SIGCHLD received", pid = 506 2021-06-16 13:09:49.354932034 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_29 msg = "Child terminated", pid = 506, status = "successfully" 2021-06-16 13:09:49.354944754 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_1 func_name = "eventd_policy_action_next" 2021-06-16 13:09:49.354989194 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_1 func_name = "eventd_policy_action_next" 2021-06-16 13:09:49.354998454 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_1 func_name = "eventd_policy_action_next" 2021-06-16 13:09:49.355005984 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_3 msg = "removing active policy", PolicyName = "backup_config" 2021-06-16 13:09:49.355115774 re0:master-eventd:10911:TRACE_ERR EVENTOPTIONS_TRACE_POLICY_P_EVENTOPTIONS_TRACE_POLICY_28 msg = "SIGCHLD received", pid = -1 ...
You can include the terse option to display just the timestamp and
message.
content_copy zoom_out_map
user@host> show trace application master-eventd terse 2021-06-16 13:09:47.320304999 msg = "policy should now be executed", policy = "backup_config" 2021-06-16 13:09:47.320324689 msg = "Executing Policy", policy = "backup_config" 2021-06-16 13:09:47.320348369 func_name = "eventd_policy_action_next" 2021-06-16 13:09:47.320365189 func_name = "eventd_policy_action_next" 2021-06-16 13:09:47.320372819 func_name = "eventd_policy_action_next" 2021-06-16 13:09:47.320438179 msg = "executing commands", PolicyName = "backup_config", evt_id = "UI_COMMIT_COMPLETED", cmd_file = "/tmp/evt_cmd_vfEgUQ", output_file = "/tmp/evt_op_gDnEpr" 2021-06-16 13:09:47.320464959 func_name = "eventd_substitute_variable_cmd" ...
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:
content_copy zoom_out_map
[edit] user@host# set system trace application master-eventd node re0 level notice user@host# commit
For more information about configuring trace settings, see trace.
