store
Syntax
store {
database;
file name {
files number;
(no-world-readable | world-readable);
size size;
}
fwding-file name {
files number;
(no-world-readable | world-readable);
size size;
}
}Hierarchy Level
[edit system resiliency]
Description
Store exception data in a file or database.
The on-box collector is disabled by default.
To enable the on-box collector for forwarding exceptions and store the exception data in a file, configure the following:
user@host# set system resiliency exceptions forwarding user@host# set system resiliency store fwding-file file-name user@host# set system resiliency store fwding-file size size
For forwarding exceptions, you must also configure inline-monitoring services to create the IPFIX records used to carry the exception data; see Understand Juniper Resiliency Interface.
To enable the on-box collector for routing and kernel exceptions and store the telemetry key-value-pair exception data in a file, configure the following:
user@host# set system resiliency exceptions routing user@host# set system resiliency exceptions os user@host# set system resiliency store file file-name user@host# set system resiliency store size size
Default
database
Options
| database |
Store exceptions data in the on-box SQLite database, in the /var/db directory. You can copy this database to a remote server and issue SQL commands using the SQLite command line interface. Starting in Release 22.2R1, you can only configure one place
to store your exception data, either in the database or in
a file on the device. You cannot store data in both
places. If you configure both the
|
| file file-name |
Use the specified file to receive the telemetry exceptions data. All files are placed in the directory /var/log. The files are also archived in the same way as trace logs. Starting in Release 22.2R1, you can only configure one place
to store your exception data, either in the database or in
a file on the device. You cannot store data in both
places. If you configure both the
|
| files files |
(Optional) Use the specified maximum number of files to
create before overwriting the oldest one. If you specify a
maximum number of files, you also must specify a maximum
file size with the
|
| fwding-file file-name |
Use the specified file to receive the forwarding IPFIX exceptions data. All files are placed in the directory /var/log. The files are also archived in the same way as trace logs. Starting in Release 22.2R1, you can only configure one place
to store your exception data, either in the database or in
a file on the device. You cannot store data in both
places. If you configure both the
|
| no-world-readable |
(Default) Disable unrestricted file access. This means the exceptions file can be accessed only by the user who configured the exceptions operation. |
| world-readable |
(Optional) Enable unrestricted file access. |
| size size |
(Optional) Use the specified maximum size of each file. By
default, the number entered is treated as bytes.
Alternatively, you can include a suffix to the number to
indicate kilobytes (KB), megabytes (MB), or gigabytes
(GB). If you specify a maximum file size, you also must
specify a maximum number of files with the
|
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 21.2R1 for MX Series routers.
Statement introduced in Junos Evolved OS Release 22.2R1 for PTX Series routers.