Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Reporting for Puppet Agents Running Junos OS

You can require a Puppet agent to compile reports containing the log messages and metrics that are generated during configuration updates. To require that the Puppet agent report to the server after each transaction, you must set the agent report value to true in the puppet.conf file. If you enable reporting, by default, the agent node sends a YAML-formatted transaction report to the same server from which it downloads its configuration.

Puppet log messages can identify the source, severity level, and timestamp of the message, information about the operation or error that generated the message, and any tags associated with that operation or error. The Puppet agent always generates log messages with a severity level of notice, info, or err as part of a normal update. To generate log messages with a severity level of debug, you must specify the --debug option when you run the Puppet agent.

The Junos OS provider code for the netdev_stdlib_junos module designates log entries specific to Junos OS processing with source: JUNOS. Table 1 describes the Puppet agent reporting logs generated for Junos OS operations.

Table 1: Puppet Agent Reporting Logs for Devices Running Junos OS

Severity Level

Operation

Message Content

Tags

debug

configuration changes

Junos OS configuration changes in XML format.

debug, config, changes

debug

operational updates

Information concerning the operation, for example: "Opening a local connection: jex.example.com".

debug

err

commit operation failed

Reason for failed commit.

config, fail

info

commit operation requested

Number of configuration changes.

config, commit

notice

configuration changes

Junos OS configuration changes in a diff format.

config, changes

notice

commit operation successful

Commit success message.

config, success

The following examples show sample log messages generated by a Puppet agent while performing a configuration update.

  • The following sample log message shows that the Puppet agent requested a commit operation involving one change to the configuration:

  • The following sample log message shows that the Puppet agent requested the specified update to the configuration. The message only displays the configuration differences.

  • The following sample debug log message shows that the Puppet agent requested the specified update to the configuration. This is the same configuration request as in the previous example, but in this case, the message displays the configuration data using XML format. To generate log messages with a severity level of debug, you must specify the --debug option when you run the Puppet agent.

  • The following sample log message shows a successful commit operation on the agent node: