In my previous article, I talked about bandwidth monitoring between the PRTG core server and remote probe, and I mentioned the possibility of monitoring the number of sensors on each probe system and visualizing them on the map. As promised, the goal of today's article is to show you how to do it.
Since the start of the Green IT discussions about 15 years ago, the topic of data center energy efficiency has gained considerable importance. In the mid-2000s, hardly any IT managers were aware of how much energy their IT and, in particular, their data center required. Today, 85 percent of IT managers can name their annual power requirements. This change in awareness was also necessary because a data center's power consumption share is considerable. For this reason, many companies have taken measures to improve energy efficiency. On the one hand, this can mean a significant reduction of costs, but on the other hand, it also contributes to climate protection.
PRTG 21.2.67 has been available in the stable release channel since last week. With this version, we released the probe-independent Core Health (Autonomous) sensor, as well as three new experimental sensor types*: two HPE 3PAR sensors and a Beckhoff IPC System Health sensor.
Generally speaking, gateways represent links between systems that are not necessarily compatible, and thus enable communication between them. In this context, the term "system" can refer to networks, individual computers, networked devices, or even various applications. So, for example, a fax machine that receives an incoming fax and forwards it as an e-mail could be considered a gateway.
This article is part 2/2 about the protocols, gateways, and data transmission methods relevant in building state monitoring. In part 1/2 we went into details about the philosophy of building state monitoring and the various popular protocols, already telling some details about data transmission. Now let's have a look at gateways and, more importantly, the large field of data transmission methods.
In an industrial environment, several components of industrial automation are connected, and these components need to communicate with one another. Historically, this communication was done using Fieldbus, and the components were connected using serial-based communications. Data transfer was done through protocols like Modbus, PROFIBUS, CAN bus, and others.
Imagine you plan to add several network switches to your PRTG environment. But you only want to add sensors for interfaces that are connected. Until now, this required some manual effort. Since PRTG 21.1.65, you can now customize the PRTG auto-discovery with filter criteria. This allows you to precisely define in advance which sensors auto-discovery should add, and which it should not.
One of the questions we often hear is: How much bandwidth do the PRTG core server and remote probe consume in a specific time frame, and how can we visualize it on a dashboard? Well, there is no single answer here. It depends on a few factors, such as the number of remote probes, the number of sensors and channels, as well as the scanning interval. For example, 100 SNMP sensors, each with 2 channels (in & out) generate roughly 1 kbit/s plus 20 bytes/minute (due to the core "keep-alive" message). This reflects a daily load of about 11 MB a day. If you´d like to see the math behind this number, please check this page.
As you’ll have seen in our first article, IP Fabric provides administrators with a thorough, end-to-end view of their network. Relationships and interactions between devices are correlated, intent verification rules are confirmed, and regulatory compliance validated. In this article, we’re going to take a deeper, more technical look at how PRTG can utilize information from IP Fabric, and combine it with its own data to help give network admins a detailed look at not just how their environment is performing, but how it’s actually behaving – is it handling traffic efficiently, securely and in the way it’s supposed to?
It's been about 5 years since we moved into our new headquarters in Nuremberg, and, starting in 2017, we've not only implemented facility-wide monitoring of room air quality (involving various sorts of sensors), but also a respectable PV system. Check out how we came to be where we are now – a completely monitored office building – and how exactly we generate the data that shows a lot about how we work and what our company purposes are.
Telchemy & Paessler – Keeping Everyone Talking Since my great-great-great-grandfather, Alexander Graham Bell*, patented the first telephone in 1875, the technology has become a key part of business communications (*OK, so we’re not actually related). The technology may have evolved enormously over the intervening 144 years, but the basic idea remains the same – keep everyone talking.
As networks become ever more critical to the operation of your business, complexity continues to increase. So you need to be sure that PRTG is genuinely giving you full visibility of all network devices. IP Fabric can help you answer the question, "Am I really monitoring all of my network"? Walk with me and I'll explain how.
The attack on a water company in Oldsmar, Florida, is an almost textbook illustration of the security flaws that still prevail in many critical infrastructures. The lack of damage from the attack was a lucky coincidence rather than due to a thorough security concept. The incident underscores the need for intelligent, real-time monitoring in critical infrastructure.
VQM (voice/video quality monitoring) is an advanced monitoring methodology used to mitigate and resolve performance-affecting issues before they become catastrophic. VQM works by leveraging both active (synthetic) and passive (live call/session) testing and analysis. With typical premise-based Unified Communications (UC) implementations, voice and video conferencing application traffic travels over the organizations existing LAN/WAN infrastructure.
This article is part 1/2 about the protocols, gateways, and data transmission methods (as well as wireless protocols) relevant in building state monitoring. But let's first start with the philosophy behind it all, which is mainly based on manufacturer independence and open systems.