close

keyboard_arrow_left

Table of Contents Expand all

list Table of Contents

English

process (Memory)

date_range 09-Dec-23

arrow_backward

arrow_forward

Syntax

content_copy zoom_out_map
process {
    frequency (minutes | hours | days) value;
    minor-event {
        threshold process name memory-limit value ;
        action snmp-trap;
    } 
    major-event {
        threshold process name memory-limit value ;
        action [snmp-trap | live-core | (terminate-process| terminate-process-force)];
    }
    critical-event {
        threshold process name memory-limit value ;
        action [snmp-trap | live-core | (terminate-process| terminate-process-force)];
    }
}

Hierarchy Level

content_copy zoom_out_map
[edit system monitor memory]

Description

Configure process level memory monitoring. Because you cannot specify a threshold for all processes, an algorithm (heuristics-based) is used to identify the processes that are likely to cross the threshold. The algorithm can identify the processes based on learning the memory growth pattern of the processes and comparing the memory usage of the processes with the baseline of the process. The algorithm measures the virtual memory footprint, increase in memory foot print since baseline, and memory growth pattern score to identify the processes. You can also specify exceptions. Learning is always on at the configured time interval for process monitoring. Also, prediction is possible only when the module is aware that the system is running low on memory.

The remaining statements are explained separately.

Options

frequency	Specify the frequency of system level memory monitoring. You can specify the frequency in days, hours or minutes. Possible values: 1 through 65535.
minor-event	Indicates a non-critical event that, if left unchecked, may cause an interruption in service or degradation in performance but does not significantly affect the device.
major-event	Indicates an event that, if left unchecked, may result in significant loss of service or interruption of traffic.
critical-event	Indicates an event that, if left unchecked, may result in serious loss of service or interruption of traffic. In case a critical event is triggered, you can terminate the process but only if the device is running out of memory.

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 20.1.

arrow_backward PREVIOUS process-inform

NEXT arrow_forward process-monitor

Junos CLI Reference

ON THIS PAGE

process (Memory)

Syntax

Hierarchy Level

Description

Options

Required Privilege Level

Release Information

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Junos CLI Reference

ON THIS PAGE

process (Memory)

Syntax

Hierarchy Level

Description

Options

Required Privilege Level

Release Information

Related Documentation

Stay in touch