...
- Device Initiated - restarts initiated by the DataPower due to a reason (like e.g. low memory)
- User Initiated - a restart that was initiated by a user via the web interface, CLI, etc.
- Unexpected - for example, due to a power failure
- Domain Restart - a user initiated domain restart
DPOD analyzes the restarts by reading the monitored device's audit logs every 15 minutes, you can change this interval from through the Web Console by navigating to Manage→System Parameters→Interval in Seconds to Analyze Audit Logs.
The dashboard consists of Restarts Dashboard comprises 4 parts:
- A graph showing the restarts over a timeline
- The Device memory graph (a device initiated restart is often related to memory issues)
- Device and domain restarts table
Last sample time table
Restarts Timeline
The chart shows all the restarts on a timeline.
Zoom over a specific part of the graph to reload apply the page with this time period as a filter.
Click on the restart cause (Device Initiated, User Initiated, etc.) in the legend to reload the page with this restart cause as a filter.
...
The table shows all the restarts in a chronological order.
| Note |
|---|
| In case When one of the devices was not sampled or analyzed, an error message will appear in the table's header , next to alongside the title. It may suggest that one of the devices is currently experiencing downtime. Check the "Last sampling time" table at the bottom of the page for more information. |
...
Last Sampling Time and Sampling Errors Table
The This table shows when was the last time DPOD was reading readi and analyzing analyzed the audit logs for each monitored device
| Column | Description |
|---|---|
| Device | The monitored device name |
| Last Sample Time | The last time DPOD accessed the device audit logs |
| Last Analyze Time | The last time DPOD analyzed the audit logs |
| Errors | Lists any error errors that occurred - for example, , e.g. "Could not connect to host" |
...