User Tools
Writing /app/www/public/data/meta/resolution_area/prometheus_resolutions/res-p1402.meta failed
resolution_area:prometheus_resolutions:res-p1402
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-p1402 [2021/06/24 15:10] – btobin | resolution_area:prometheus_resolutions:res-p1402 [2021/12/21 11:10] (current) – wflaherty | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | =====CriticalDiskSpace===== | ||
| + | **Level:** __Critical__ FIXME | ||
| + | |||
| + | |||
| + | **Purpose: | ||
| + | |||
| + | **Scenario: | ||
| + | |||
| + | **Resolution: | ||
| + | |||
| + | **Manual Action Steps:** | ||
| + | |||
| + | Depending on the size of the disk and the role of the server, this may be very serious or not as serious. | ||
| + | If there are still 400GB of a 4TB disk then its not so bad. However, if the disk is rapidly filling and might reach max capacity, we will have to be quick and stop any application that might be doing that. | ||
| + | |||
| + | Ensure you check the size of the log files. | ||
| + | |||
| + | See some of the steps outlined [[http:// | ||
| + | |||
| + | |||
| + | |||
| + | **Auto Clear:** Possible. | ||