CPU or Memory Overload
Change Review
- Has there been an increase in:
- Traffic volume
- Logging verbosity
- Service or application configurations?
Diagnostic Actions
- Review system usage through Performance Monitor or InControl dashboards.
- Identify high-usage processes consuming CPU or memory.
- Capture network traffic to detect floods or scans.
- Look for indicators of DoS attacks or traffic anomalies.
- Reduce logging levels or redirect logs to an external syslog server so it is possible to followup on.
- Restart resource-intensive services cautiously.
- Reference this KB article for advanced analysis: https://kb.clavister.com/324736260
Recovery Milestones
- CPU and memory usage returns to a stable state.
- Overload identified as external (e.g., a DoS attack).
- Adjustments or rollback stabilize system behavior.
Related articles
No related articles found.