Tracing APPID Operations
Tracing operations track all adaptive services operations and record them in a log file. The logged error descriptions provide detailed information to help you solve problems faster.
By default, no events are traced. If you include the traceoptions statement at the [edit services application-identification] hierarchy level, the default tracing behavior is as follows:
- Important events are logged in a file called serviced located in the /var/log directory.
- When the file serviced reaches 128 kilobytes (KB), it is renamed serviced.0, then serviced.1, and so on, until there are three trace files. Then the oldest trace file (serviced.2) is overwritten. (For more information about how log files are created, see the Junos OS System Log Messages Reference.)
- Only the user who configures the tracing operation can access the log files.
- To display the end of the log, issue the show log serviced | last operational mode command:[edit]user@host# run show log serviced | last
You cannot change the directory (/var/log) in which trace files are located. However, you can customize the other trace file settings by including the following statements:
You configure these statements at the [edit services application-identification traceoptions] hierarchy level.
These statements are described in the following sections:
Configuring the APPID Log Filename
By default, the name of the file that records trace output is serviced. You can specify a different name by including the file statement at the [edit services application-identification traceoptions] hierarchy level:
Configuring the Number and Size of APPID Log Files
By default, when the trace file reaches 128 kilobytes (KB) in size, it is renamed filename.0, then filename.1, and so on, until there are three trace files. Then the oldest trace file (filename.2) is overwritten.
You can configure the limits on the number and size of trace files by including the following statements at the [edit services application-identification traceoptions] hierarchy level:
For example, set the maximum file size to 2 MB, and the maximum number of files to 20. When the file that receives the output of the tracing operation (filename) reaches 2 MB, filename is renamed filename.0, and a new file called filename is created. When the new filename reaches 2 MB, filename.0 is renamed filename.1 and filename is renamed filename.0. This process repeats until there are 20 trace files. Then the oldest file (filename.19) is overwritten by the newest file (filename.0).
The number of files can be from 2 through 1000 files. The file size of each file can be from 10 KB through 1 gigabyte (GB).
Configuring Access to the Log File
By default, only the user who configures the tracing operation can access log files.
To specify that any user can read all log files, include the file world-readable statement at the [edit services application-identification traceoptions] hierarchy level:
To explicitly set the default behavior, include the file no-world-readable statement at the [edit services application-identification traceoptions] hierarchy level:
Configuring a Regular Expression for Lines to Be Logged
By default, the trace operation output includes all lines relevant to the logged events.
You can refine the output by including the match statement at the [edit services application-identification traceoptions file filename] hierarchy level and specifying a regular expression (regex) to be matched:
Configuring the Tracing Flags
By default, if the traceoptions configuration is present, only important events are logged. You can configure the trace operations to be logged by including the following statements at the [edit services application-identification traceoptions] hierarchy level:
Currently, the only supported flag is all, which instructs the router to trace all operations.
