PRTG Network Monitor
News From Paessler
With the release of PRTG Network Monitor version 21.4.73, which has been available since December 1st, we are happy to announce a lot of great news at once: A new, modern web interface A brand-new RESTful API A new multi-platform probe New OPC UA notification options 4 more sensors in experimental states ?? Please note that all new additions are early alpha versions whose development is not yet complete, and thus not all features are included. Let's take a look at the details!
For a long time “Security through obscurity” was the mantra of the OT Engineer. If a device or network can’t be accessed, it can’t be attacked. Unfortunately, with today’s push towards convergence, this can no longer be relied upon. Actually knowing what assets are in the network can be a big problem in the OT world.
I recently wrote an article that explains how much bandwidth is consumed between the PRTG core server and remote probes. For the sake of context, a few years ago our reseller Omicron AG from Switzerland set up an installation of PRTG with 10,000 SNMP sensors for one of their customers. Within minutes, they could see that they were only generating 400 kbit/s of network traffic for 10,000 sensors with a one-minute scanning interval (which is less than 3 kbit/s per switch)! If you missed it, you can read it here.
Okay, two things are probably clear. We publish outstanding use cases on our blog every now and then – and both PRTG Network Monitor and PRTG Enterprise Monitor are, to varying degrees, made to monitor large IT environments, providing a simple way to gain visibility and control over increasingly complex infrastructures. This is the last part of a four-part series. Are you proudly old school, don't like this newfangled blogging, and would prefer to have your use case as a proper PDF? Who could blame you? You will find the linked PDF on this use case page. iAbout LNA Santé With 30 years of experience, LNA Santé focuses on improving the quality of life for people of any age who are dealing with temporary or permanent medical conditions by providing a welcoming and caring environment. Committed to providing quality services and guided by its mission to "cure and take care", LNA Santé has seen growth in its various undertakings. As of June 30, 2020, the organization has more than 6,500 employees in 72 establishments: 45 nursing homes (called EHPAD in French) with 4,631 beds in France, 4 nursing homes in Belgium (with 555 beds) for the long-term care sector, 15 follow-up care and rehabilitation centers (2,286 beds), a psychiatric clinic (211 beds) and 7 home hospitalization facilities (473 places) for the medium-stay sector.
These days, REST APIs are just about everywhere. Everything from gateways and firewalls through to ticket systems and weather sites offer REST APIs that let you query information. This represents an opportunity to bring even more data into your monitoring concept. Think of examples like monitoring weather conditions using APIs of online weather sites, or the number of open tickets in your ticket system. To help you harness the flexibility that REST offers, Paessler PRTG provides you with the REST Custom Sensor V2 as part of its monitoring solution.
Compared to the last releases of PRTG Network Monitor, this update does not contain many new sensors, but features several fixes and improvements. It comes with the experimental AWS Alarm v2 sensor and security improvements for SQL v2 sensors.
Okay, two things are probably clear. We publish outstanding use cases on our blog every now and then – and both PRTG Network Monitor and PRTG Enterprise Monitor are, to varying degrees, made to monitor large IT environments, providing a simple way to gain visibility and control over increasingly complex infrastructures. This is part 3 of a four-part series. Are you proudly old school, don't like this newfangled blogging, and would prefer to have your use case as a proper PDF? Who could blame you? You will find the linked PDF on this use case page. iThe School District of Pickens County (SDPC) is located in the northwestern region of South Carolina. SDPC includes 14 elementary schools, five middle schools, four high schools, and a state-of-the-art career and technology center. There are over 16,000 students enrolled in SDPC schools and over 2,000 employees. SDPC strives to provide a quality 21st century education that prepares all students for success beyond the classroom.
With 12 million active users daily and 156,000 organizations subscribed to the app (in 2021), Slack is one of the most popular and rapidly growing apps to connect teams, unify their systems, and drive their business forward. It is integrated into the Paessler PRTG monitoring notification system, which means, in the case of data center outages, PRTG can trigger notifications and send them directly to the Slack channel(s) you want. This sounds convenient, doesn't it? There are also many other notification types you can try, which we covered in other articles that are listed at the end of this article.
Modbus. It’s a fieldbus protocol that’s been around longer than many of the engineers and technicians who use it. And yet it isn’t going away. Even in 2021, the two common variants of Modbus – Modbus TCP and Modbus RTU – make up 10% of the industrial network market. This is one of the reasons why we included Modbus functionality in our Paessler PRTG monitoring software. We previously wrote about how you can use Modbus TCP as part of your industrial monitoring with PRTG; since then, we also added Modbus RTU capability to PRTG. But what advantages does monitoring with Modbus bring? We’ll get to that. But first, let’s take a look at examples of how you’d use Modbus in your monitoring concept.
Update October 2021: It’s that time again – there are new VISA cards available. Each worth $25, for every published and accepted review at the Gartner Peer Insights for IT Infrastructure Monitoring Tools. If you would like to write a review, please use the following link: ?? https://gtnr.io/lceiYDIPE Thanks for your support! ---
To ensure the smooth operation of a data center, your first priority is to avoid errors and problems with the server hardware. In the age of virtualization, it is crucial to keep an eye on the hypervisors and to eliminate incipient problems before they lead to malfunctions or even failures - regardless of which manufacturer your server hardware is made by.
If you monitor your server hardware in your data center with PRTG, you are probably familiar with the System Health Sensor for hardware like Dell, HP, Lenovo, etc., which allows you to monitor the status of the CPU fan, the battery, and also overall system status, among other things. Each sensor includes numerous channels that let you keep a detailed eye on your hardware. But did you know that PRTG also lets you monitor the system health of your server hardware via the Redfish protocol?
The concept of Closing the Loop in itself is very simple. For every workplace device a customer buys, a corresponding amount of electronic waste is recycled – with a clear focus on Africa, where electronic waste is a ubiquitous problem. In the pre-Corona year of 2019 alone, the world accumulated 53.6 million tons of e-waste. That's an almost indescribably large number. And the annual amount of electronic waste will continue to increase, as also stated by the Global E-Waste Monitor 2020. Those that suffer the most from this development are developing countries. When we found out about Closing the Loop, it was clear to us that we wanted to be a part of it. After all, if you read our blog regularly, you know that we are committed to the reduction of resource consumption.
Did you feel that moment of wondering when you were told that your new applications would be hosted in the cloud? I did. At what point did you really feel ready to manage them?
Syslog – One log to rule them all. Calling all Sysadmins - I hope you have December 3rd marked down in your diaries this year? On that day, one of the most vital, but undervalued utilities in the admin’s toolkit turns 18. The first draft of the Syslog protocol was published by the IETF on that date, in 2003.