traceoptions (REST API)
Syntax
traceoptions {
flag flag;
}
Hierarchy Level
[edit system services rest]
Description
Enabling tracing can adversely impact scale and performance and may increase security risk. We strongly recommend using the trace, tracing, or traceoptions commands only under the guidance of a JTAC support engineer. After collecting the debug information, immediately disable tracing to minimize risk and restore normal system performance.
Define tracing operations for the REST API service.
Options
flag flag—Tracing operation to perform. To
specify more than one tracing operation, specify all. REST API
tracing options include:
-
all—All tracing operations. A combination of the juise and lighttpd tracing operations. -
juise—Trace juise operations. Trace information is captured in /var/chroot/rest-api/var/log/juise. -
lighttpd—Trace lighttpd operations. Trace information is captured in /var/chroot/rest-api/var/log/lighttpd.
The REST API traceoptions do not support parameters to control
log file size or the number of log files.
The juise trace log uses a default rotation setting:
size=10m, files=10.
The lighttpdtrace log writes to a single file without any size
limit.
On MX Series platforms, both logs are stored in
/var/jails/rest-api/log/.
If left enabled for extended periods, lighttpd tracing may cause
the log file to grow indefinitely, potentially leading to filesystem full
conditions or software upgrade failures.
Required Privilege Level
system—To view this statement in the configuration.
system-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 14.2.