Usually when there is a wildcard like (““) at the beginning of the pattern, Juniper SRX expects a character before the wildcard which can be matched one or multiple times. When we use a custom pattern with nothing preceding the wildcard (““) the device will experience core dump.
For a project, I had to gather data in order to measure the SRX performance under different traffic loads. This was done for a SRX chassis system in cluster mode. The following commands were utilized in order to capture metrics when the system was subjected to traffic load:
show system uptime show system statistics show chassis routing-engine show chassis fpc show chassis cluster status show chassis cluster information show chassis cluster interfaces show security monitoring show security monitoring performance spu show security flow statistics show interfaces reth0 statistics show security monitoring fpc node all <fpc-slot>
Github with scripts to execute the above commands and save it in a file.