User Tools
Writing /app/www/public/data/meta/resolution_area/prometheus_resolutions/res-p1601.meta failed
resolution_area:prometheus_resolutions:res-p1601
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| resolution_area:prometheus_resolutions:res-p1601 [2021/06/24 15:13] – btobin | resolution_area:prometheus_resolutions:res-p1601 [2021/07/06 12:47] (current) – 10.91.120.28 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | =====UnusualNetworkThroughputIn===== | ||
| + | **Level:** Warning | ||
| + | |||
| + | |||
| + | **Purpose: | ||
| + | |||
| + | **Scenario: | ||
| + | |||
| + | **Resolution: | ||
| + | |||
| + | **Manual Action Steps:** Assuming everything was normal then the thresholds can be edited in the prometheus.rules file in the prometheus-monitoring-config project. Otherwise another investigation would need to be carried out on the unusual traffic. | ||
| + | |||
| + | You could use //tcpdump -i eth0// to see whats going on at the eth0 interface | ||
| + | |||
| + | **Auto Clear:** This will clear once the threshold is no longer breached | ||