Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Logging and Notifications

Read this topic to learn about logging and notification functions in Juniper Cloud-Native Router. We discuss the location of log files, what you can log, and various log levels. You can also learn about the available notifications and how the notifications are implemented in the Cloud-Native Router.

Logging

The system stores log files from all the Cloud-Native Router pods and containers in the log_path directory. You can configure the location of the log files at the deployment time by retaining or changing the value of the log_path key in the values.yaml helm chart. By default, the location of the log files is /var/log/jcnr.

The Juniper Cloud-Native Router pods and containers use syslog as their logging mechanism. The syslog-ng pod stores event notification data in JSON format on the host server. By default, the file location is /var/log/jcnr and the filename is jcnr_notifications.json. You can change the location and filename by changing the value of the syslog_notifications key in the values.yaml helm chart when installing the Cloud-Native Router. You can disable syslog logging by configuring the installSyslog parameter as false in the values.yaml helm chart. Please review the Customizing Cloud-Native Router Helm Chart for more details.

When you use the default file locations, the /var/log/jcnr directory displays the following files:

Note: The host server must manage the log rotation for the contrail-vrouter-dpdk.log and the jcnr-cni.log files.

Notifications

The syslog-ng pod continuously monitors the preceding log files for notification events such as interface up, interface down, interface add, and so on. When these events appear in a log file, syslog-ng converts the log events into notification events and stores the events in JSON format within the syslog_notifications file configured in the values.yaml file.

Here is a sample of syslog-ng notifications:

Table 1: Supported Notifications
Notification Source Pod

License Near Expiry​

 cRPD

License Expired

 cRPD

License Invalid​

 cRPD

License OK​

 cRPD
License Grace Period cRPD
License Not Present cRPD

Cloud-Native Router Init Success​

 Deployer

Cloud-Native Router Init Failure​

 Deployer
Cloud-Native Router Graceful Shutdown Request Deployer
Cloud-Native Router Graceful Shutdown Complete Deployer
Cloud-Native Router Graceful Shutdown Failure Deployer
Cloud-Native Router Restart Deployer
Cloud-Native Router Upgrade Success Deployer
Cloud-Native Router Upgrade Failure Deployer

Upstream Fabric Bond Member Link Up​

 vRouter

Upstream Fabric Bond Member Link Down​

 vRouter

Upstream Fabric Bond Link Up​

 vRouter

Upstream Fabric Bond Link Down​

 vRouter
Upstream Fabric Bond Link Switchover vRouter

Downstream Fabric Link Up​

 vRouter

Downstream Fabric Link Down​

 vRouter

Appliance Link Up​

 vRouter

Appliance Link Down​

 vRouter

Any Cloud-Native Router Application Critical Errors​

 vRouter
Any Cloud-Native Router Application Warnings vRouter
Any Cloud-Native Router Application Info vRouter
Cloud-Native Router Rate Limits Reached vRouter

Cloud-Native Router MAC Table Limit Reached​

 vRouter

Cloud-Native Router CLI Start​

 cRPD or vRouter-Agent

Cloud-Native Router CLI Stop​

 cRPD or vRouter-Agent

Cloud-Native Router Kernel App Interface Up​

 vRouter

Cloud-Native Router Kernel App Interface Down​

 vRouter

Cloud-Native Router Virtio User Interface Up​

 vRouter

Cloud-Native Router Virtio User Interface Down​

 vRouter
Purel2 Macmove Loop Detected vRouter