You can now see the specific scanning times of a sensor if you have defined them as described in In this case, the scanning interval is named Irregular and shows the scanning times in a tooltip.You can now share the graphs page with a URL link.We fixed an issue for sensor channel values that were sometimes displayed in too large numbers. We fixed an issue in the sensor graphs section to avoid the risk of possible cross-site scripting (XSS) attacks. The mobile view now shows channels with unknown lookup states. You can now resume acknowledged alarms for sensors using the Clear Acknowledged Alarm button via the context menu and bulk edit change.The basic settings of a device include Status, IPv4 Address/DNS Name, IP Version, Device Name and Priority. You can now change the basic settings of a device in the Basic Device Settings section.This way you can create your own custom script sensors that may not be available in PRTG by default.įor available example scripts and how to use them, please see the Knowledge Base article: The sensor executes a Python script that returns data in JSON format and shows the exit code. You can try out the experimental Script v2 sensor that also works on the Multi-Platform Probe. The sensor still shows the Status channel as the primary channel if you enabled the Inverted Error Status feature when creating the sensor. The Response Time channel is now set as the primary channel for the Ping v2 sensor if you created the sensor with Inverted Error Status disabled and multiple pings. Previously, the sensor did not report an error even if the requested HTTP page did not respond within a certain limit of time. We fixed an issue with the timeout setting in the HTTP v2 sensor.As a result, the Post Body field is no longer marked as a required field when you select POST as Request Method. We fixed an issue in the multi-edit menu that caused an error in the required fields validation for the post body.We are investigating the cause of this issue. The error may come up during authentication on the target device. In certain configurations, the Windows MSMQ Queue Length sensor reports an error with the message Queuename not found on specified machine. As a workaround, please use an internal non Single Sign-On user account to view PDF file reports. The opened page shows the message Unauthorized instead of the report data. With PRTG version 23.x.82, reports currently cannot be opened correctly for the option Create and store PDF and data files and Create and store PDF and data files and send them by email when you are logged in to PRTG via Single Sign-On. We will deliver a fix for this issue with an upcoming PRTG version. If you primarily use special characters or Asian and Cyrillic characters in your email notifications, we recommend that you do not update your PRTG installation to version 23.1.82. The subject of email notifications is not correctly displayed in the current PRTG version if it contains special characters like diacritics or umlauts.
0 Comments
Leave a Reply. |