Seeing latency spikes in our pipelines during Firebox deployments. Traffic isn't heavy. Spikes are random, 200-500ms jumps, then back to normal.
Need to isolate: is it the Firebox policy processing, the network path, or our monitoring?
Steps I've taken:
* Confirmed spikes correlate with no internal load.
* Basic policy log check shows no obvious blocks during spike times.
What's the most efficient way to trace this?
1. Should I run a continuous packet capture on the Firebox interface and correlate with latency graphs?
2. Are there specific Firebox CLI commands to monitor real-time session latency or processing delay?
3. Known issues with specific deep packet inspection settings causing intermittent CPU hits?
My gut says it's a inspection-related queue, but I need data. Prefer CLI/Web UI methods over guesswork.