Yes. up.time uses a series of different background applications, all of which are multi-threaded.
Apache: the up.time apache engine spawns several instances, each of which will run on separate CPUs, if available. MySQL: the up.time MySQL engine spawns a single process that will run multiple queries across as many CPUs as possible. At times the MySQL threading may need tuning via the concurrent_threads MySQL system variable. Generally 2 concurrent threads per CPU core is recommended. Java: the up.time data collector is Java-based. Java is inherently multi-threaded so up.time service monitors and other tasks will be spread across many CPUs. |
'Default up.time data store' monitor crit after adding a vCenter ... | Rating | Views | |
---|---|---|---|
As part of the initial install of up.time, the Monitoring Station itself is setup as an element within up.time. This sample element is initially setup to use localhost as it's hostname, along... By: uptime Support | Date Created: 3-8-2013 | Last Modified: 3-8-2013 | Index: 592 |
3022 |
Integrating up.time NetFlow with up.time | Rating | Views | |
---|---|---|---|
Learn how to configure up.time to point to your Scrutinizer instance to enable click-through graphing, as well as an integrated Scrutinizer view from Global Scan. By: uptime Support | Date Created: 7-8-2010 | Last Modified: 2-8-2013 | Index: 459 |
5658 |
Monitoring WebSphere with up.time | Rating | Views | |
---|---|---|---|
Use up.time to monitor the performance and health of Java applications running on WebSphere servers. By: uptime Support | Date Created: 12-20-2006 | Last Modified: 7-26-2011 | Index: 108 |
7108 |
The up.time Data Collector is unavailable | Rating | Views | |
---|---|---|---|
By: uptime Support | Date Created: 6-9-2006 | Last Modified: 10-17-2013 | Index: 077 |
6545 |
Resolving JVM_BIND Errors in up.time | Rating | Views | |
---|---|---|---|
By: uptime Support | Date Created: 6-7-2006 | Last Modified: 8-9-2011 | Index: 075 |
9686 |