These two infrastructure models can also be resized as needed. This is especially so if Cloud Providers are used, given that these are scaled up virtualizations which are configured in easy-to-use cloud portals. These can often be resized as needed, and the IT team will be well aware of the limits here, often monitoring some of the performance themselves already.

VMware is an intermediary between the operating system and the hardware, and often its limits are determined based on the sizing of the application and set by the IT team when the infrastructure is established. The IT team is a great resource for obtaining these limits in general, also keeping track of such things in VMware and virtualized infrastructure models. Limits of the hardware in this case can be found in manufacturing specifications, within the operating system settings, and listed somewhere within the IT department normally. One is Bare Metal, which relies upon the traditional use of hardware to connect directly between operating system and hardware, with no intermediary. There are several major infrastructure categories which reflect common modes of operation for ThingWorx applications. For Disk, we keep track of the read and write rates of the disks used by the application as well as how much space remains on those. For Networking, we want to know the network throughput, the available bandwidth, and how capable the network cards are in general. For Memory, we want to know how much RAM is available for the application. The four main areas to monitor in this way are CPU, Memory, Networking, and Disk.įor the CPU, we want t o know how many cores are available to the application and potentially what the temperature is for each or other indicators of overtaxation.

Knowledge of the infrastructure limits help establish these monitoring boundaries, determining straightforward thresholds that indicate an app has gone too far. The primary purpose of monitoring is to determine when your application may be exhausting the available resources. Produced by the IoT Enterprise Deployment Center By Tim Atwood and Dave Bernbeck, Edited by Tori FirewindĪdapted from the March 2021 Expert Session

Iot monitor cpu usage