Below details mentioned are event details listed on a per Category basis.
|
Severity Level |
Policy ID |
Description |
Cause |
Resolution |
|
5 |
DISK.X1.1 |
DISK.X1.1: High Disk blocking at ${BUSY} percent |
DISK.X1.1: Alert when disk IO is blocking over 85 percent |
DISK.X1.1: If no user impact is observed, this is just a notification. If this is constant, user workload may be higher than what the disks can currently handle. Adding disks usually resolves disk contention. If the event persists and user impact is observed, contact Panzura Technical Support |
|
9 |
DISK.X1.2 |
DISK.X1.2: Extreme Disk blocking at ${BUSY} percent |
DISK.X1.2: Alert when disk IO is blocking over 95 percent |
DISK.X1.2: User workload may be higher than what the disks can currently handle. Adding disks usually resolves disk contention. If the event persists and user impact is observed, contact Panzura Technical Support |
|
2 |
DISK.X1.3 |
DISK.X1.3: High Disk thrashing with latency ${MSPT}ms |
DISK.X1.3: Alert when disk IO latency is over 80ms |
DISK.X1.3: If no user impact is observed, this is just a notification. If this is constant, user workload may be higher than what the disks can currently handle. Adding disks usually resolves disk contention. If the event persists and user impact is observed, contact Panzura Technical Support |
|
5 |
DISK.X1.4 |
DISK.X1.4: High Disk thrashing with latency ${MSPT}ms |
DISK.X1.4: Alert when disk IO latency is over 160ms |
DISK.X1.4: User workload may be higher than what the disks can currently handle. Adding disks usually resolves disk contention. If the event persists and user impact is observed, contact Panzura Technical Support |
|
5 |
DISK.X1.5 |
DISK.X1.5: Main disk(s) are resilvering |
DISK.X1.5: Alert when a RAID rebuild is in progress when intermittent cloud transport checksums fail |
DISK.X1.5: If the event persists and user impact including system performance is affected, contact Panzura Technical Support |
|
4 |
DISK.X1.6 |
DISK.X1.6: Disk IO blocking is between 40 and 85 percent |
DISK.X1.6: Alert when the disk IO blocking is between 40 and 80 percent |
DISK.X1.6: If no user impact is observed, this is just a notification. If this is constant, user workload may be higher than what the disks can currently handle. Adding disks usually resolves disk contention. If the event persists and user impact is observed, contact Panzura Technical Support |
|
8 |
SYS.WUI1.5 |
SYS.WUI1.5: One or more disks are degraded |
SYS.WUI1.5: Alert when one or more disks are degraded |
SYS.WUI1.5: Review disk/RAID status and contact Panzura Technical Support |
|
5 |
DISK.L1.1 |
-OSE-DISK.L1.1: Disk is offline |
DISK.L1.1: Alert when a disk goes offline or has disconnected from the node |
DISK.L1.1: For RAID systems, re-attach and rebuild the RAID group. For non-RAID systems, a DR must be performed |
|
5 |
DISK.L1.4 |
-OSE-DISK.L1.4: Disk is online |
DISK.L1.4: Alert when a disk goes online or is connected to the node |
DISK.L1.4: New disks can be added via System Configuration - Disk Expansion - Discover New. For replacing failed disks in a RAID system, attaching will automatically start the rebuild of the RAID group |