Skip to main content

Remote monitoring and alerting for IoT

How tools and practices used for monitoring cloud-native services apply to solutions that use IoT devices. Add operations visibility to remote locations.

Introduction

IoT devices produce many types of information, including telemetry, metadata, state, and commands and responses. Telemetry data from devices can be used in short operational timeframes or for longer-term analytics and model building.

Many devices support local monitoring in the form of a buzzer or an alarm panel on-premises. This type of monitoring is valuable, but has limited scope for in-depth or long-term analysis. This article instead discusses remote monitoring, which involves gathering and analyzing monitoring information from a remote location using cloud resources.

Operational and device performance data is often in the form of a time series, where each piece of information includes a time stamp. This data can be further enriched with dimensional labels (sometimes referred to as tags), such as labels that identify hardware revision, operating timezone, installation location, firmware version, and so on.

Time-series telemetry can be collected and used for monitoring. Monitoring in this context refers to using a suite of tools and processes that help detect, debug, and resolve problems that occur in systems while those systems are operating. Monitoring can also give you insight into the systems and help improve them.

The state of monitoring IT systems, including servers and services, has continuously improved. Monitoring tools and practices in the cloud-native world of microservices and Kubernetes are excellent at monitoring based on time-series metric data. These tools aren’t designed specifically for monitoring IoT devices or physical processes, but the constituent parts—labeled series of metrics, visualization, and alerts—all can apply to IoT monitoring.

What are you monitoring?

Monitoring begins with collecting data by instrumenting the system you’re working with. For some IoT scenarios, the system you’re monitoring might not be the devices themselves, but the environment and the process external to the device. In other scenarios, you might be interested in monitoring the performance health of the devices themselves, both individually and at the fleet level.

Consider the task of monitoring a human cyclist riding on a road. There are many different parts of the overall system you can monitor. Some might be internal to the system, such as the cyclist’s heart rate or sweating rate. Others might be external to the cyclist, such as a slope of the road, or external temperature and humidity. These internal and external monitoring goals can coexist. The methodologies and tools might overlap, but you can recognize these different domains—a physician might care about different measurements than the bike mechanic. Monitoring tools can be used to create custom monitoring views.

For example, you might organize your metrics into the categories that are discussed in this section. The specifics of how these are structured or combined will depend on the particular domain and applications.

Device hardware metrics

Device hardware metrics are measurements of the hardware or physical device itself, usually with some sort of built-in sensor. 

Firmware

Software running on the devices includes application software as well as the system software itself, which might be the operating system, or layers of a networking stack or device drivers. 

Application code

Application code on the device is specific to the role that device is performing in the system. 

External environment

Measuring the environment with sensors is often what people think about with regard to IoT devices. 

Cloud device interactions

An IoT solution is a complex system that includes software components that run both on the device and in the cloud. Understanding how these two systems interact requires you to understand what information each side has access to and how to bridge the two software runtime environments. 

Supporting systems

A complete monitoring solution requires monitoring both core and supporting components. Monitoring the application code on the device is an example of whitebox monitoring, where you’re interested in how the application is functioning. You probably also want to include some blackbox monitoring. For example, your monitoring software can probe APIs and other cloud services that your solution depends on. When you’re trying to respond to a problem, having these blackbox probes in place can lead to much faster resolution. 

Alerting

Alerting is about getting warnings or notifications, and helps draw your attention to important conditions. These in turn often lead you to check visualizations and often the associated log information.

A problem with alerting is that humans are good at learning to ignore annoying “noise” (think of traffic noise, repetitive emails, and so on). Alerts are only valuable if they can be responded to and then appropriately dismissed. If an alert reports an issue that can’t be addressed, the information in the alert should instead be another metric or visualization.

Source:

https://cloud.google.com/solutions/remote-monitoring-and-alerting-for-iot
https://cloud.google.com/solutions/iot-overview#operational_information
https://prometheus.io/docs/visualization/grafana/

Managed OS – Operating System Patching & Update Processes

Overview

Quality NOC provides reactive patching to servers with both standard and managed customer operating systems. For managed servers, patches and updates are available upon request to ensure no patches are applied without customer knowledge and consent, effectively reducing risks to application and data integrity. Data and/or reports are available for you in different ways, depending on the solution used.

OS Updates

On a monthly basis, Quality NOC Cloud engineers review all recommended patches made available by operating system software vendors. A subset of these patches and updates are identified by the OS vendor as Critical or Important to installed operating systems. The most recent version of our OS is given these updates and is then re-certified by Quality NOC before it is made available to be implemented with new server builds.

Managed Server Updates

As a part of making a server managed, more updates may automatically be applied to the server. Different Linux distributions and Windows are supported. Automatic updates can be pre-agreed with the customer and discussed in weekly status meetings.

Dedicated Server and Public clouds

Dedicated Servers and Public clouds platforms can be managed by our team of system administrator, Microsoft Windows servers and Linux distribution are supported.
We have deep experience installing new applications, scripts and applying system updates, or upgrades on Red Hat, CentOS, Ubuntu, Debian, and other linux distributions.
We can coordinate with your operations or devops team and schedule downtime, and do previous snapshots befoer patching or updating your OS or applications.

Extend your operations, DevOps or development team

We do weekly meetings with our customers, we can also do short daily meetings monday to fridays and continue chat on Slack/Wire/Skype, with your operations team, devops, or developers establishing a very fluid communication and reporting about progress and/or incidents.

All-in-One Monitoring Solution

 


We can use your own monitoring systems, we can install a new system for you and migrate the hosts or if you have a small operation you can use our own monitoring system.

Our NOC team help our customers with:

  • Website Monitoring
  • Application Performance Monitoring
  • Server Monitoring
  • Network Monitoring
  • Cloud Monitoring, Private and Public

We have customers of all sizes, from a large Telecom with more than 500 hosts, mid size and small companies with only 2 hosts. Our NOC team works around the clock 24x7x365.

Our customers save resources, their engineers have more time for important projects, we improve the operations and reduce downtime.

We have a custom solution for you.

UP Time – Monitoring your systems


At Quality NOC we help you increase your up time.

We can monitor your hosts, services and storage solutions. We will get an alarms on sms or/and email when something changes and contact you immediately to inform about the issue so you can take a corrective action to solve it.

If your company does not have monitoring tools yet or are not completely configured we can also help you to with the set up .

Federico Piergentili, Founder, Quality NOC S.L., which provides remote monitoring and management 24/7 Network Operations Center (NOC) that enables monitor, troubleshoot and maintain IT environments.

Telephony Fraud – Fraud Monitoring


Telephony Fraud – Fraud Monitoring

Many people today are able to relate to an experience of opening a phone bill that causes a sharp intake of breath. But what if it was not just a couple of hundred pounds? What if it was thousands?

Telephone fraud is continuing to increase year on year and now accounts for 2% of worldwide calls which is estimated at around €40 billion a year. Businesses are falling victim to hackers, out to make money from unprotected telephone lines, and now more than ever it is essential for businesses to protect themselves.

Without the necessary protection, businesses are leaving themselves vulnerable to fraudsters capable of running up phone bills worth thousands of pounds in just a few hours!

At Quality NOC we can help you monitoring 24/7 your systems, receiving alarms and following your procedures to take care and stop the fraud reducing the risk of your business and protecting your customer relationship.

Federico Piergentili, Founder, Quality NOC S.L., which provides remote monitoring and management 24/7 Network Operations Center (NOC) that enables monitor, troubleshoot and maintain IT environments.