Why is up.time server load so high at the start of the month?|
If archiving is enabled, this is the most likely explanation. At the start of each month the up.time data archiving process starts to remove old data from your DataStore (according to your data retention setting). This process can be very resource intensive and may take a long time to complete depending on the amount of historical data to be archived.
If this problem does not clear within an acceptable timeframe, please contact uptime Support to discuss an alternate data management plan and/or disable archiving and restart the up.time Data Collector service. |
Article InfoIndex: 469 OptionsQuick Links |
up.time does not start - Java heap size too high | Rating | Views | |
|---|---|---|---|
|
|
If the up.time 4 Data Collector fails to start and messages like those below are found in the wrapper.log you may have to adjust your java heap size to a lower value. wrapper.log: ........ STATUS... By: uptime Support | Date Created: 10-10-2009 | Last Modified: 8-13-2011 | Index: 422 |
 
|
2619 |
High Availability for up.time | Rating | Views | |
|---|---|---|---|
|
Outlines various high availability options for up.time By: uptime Support | Date Created: 12-10-2012 | Last Modified: 4-10-2013 | Index: 590 |
|
3762 |
up.time fails to start after a system reboot | Rating | Views | |
|---|---|---|---|
|
This article outlines what to do when up.time services do not start after a system reboot. By: uptime Support | Date Created: 12-6-2006 | Last Modified: 7-14-2011 | Index: 106 |
|
2981 |
Unable to fully load vendor-supplied MIBs into up.time 7 | Rating | Views | |
|---|---|---|---|
|
|
How to resolve MIB dependencies (load order) with custom MIBs. The following symptoms in the up.time MIBBrowser are signs that there is an issue with the order that custom MIBs are being loaded... By: uptime Support | Date Created: 7-19-2012 | Last Modified: 7-20-2012 | Index: 580 |
|
4061 |
High CPU Usage on Windows Agent | Rating | Views | |
|---|---|---|---|
|
|
If you observe high CPU usage on systems running the Windows agent, try disabling unused counters (e.g. IIS, SQL, Exchange, etc.) and then restart the agent. If this does not resolve the issue,... By: uptime Support | Date Created: 7-12-2011 | Last Modified: 8-11-2011 | Index: 542 |
|
3004 |
