Settings and activity
2 results found
-
7 votes
Hi there,
Great news! Your idea has been approved and moved to the next stage on Paessler.
Before we can commit to developing this idea, we need more input from the community. Your idea has the potential to significantly impact our users, and getting broader feedback will help us understand its full scope and prioritize it effectively.
Here's how you can help:
- Share your idea: Encourage other Paessler users to view, comment on, and vote for your idea.
- Elaborate on your suggestion: Add more details, use cases, or examples to your idea description.
- Engage with comments: Respond to questions and suggestions from other users.
The more engagement your idea receives, the better its chances of being fully implemented.
Thanks for your continued collaboration in making Paessler even better!
Best regards,
The Paessler Product Team
An error occurred while saving the comment 
claudio saavedra
supported this idea
·
claudio saavedra
shared this idea
·
-
1 vote
Hi there,
Great news! Your idea has been approved and moved to the next stage on Paessler.
Before we can commit to developing this idea, we need more input from the community. Your idea has the potential to significantly impact our users, and getting broader feedback will help us understand its full scope and prioritize it effectively.
Here's how you can help:
- Share your idea: Encourage other Paessler users to view, comment on, and vote for your idea.
- Elaborate on your suggestion: Add more details, use cases, or examples to your idea description.
- Engage with comments: Respond to questions and suggestions from other users.
The more engagement your idea receives, the better its chances of being fully implemented.
Thanks for your continued collaboration in making Paessler even better!
Best regards,
The Paessler Product Team
claudio saavedra
shared this idea
·
WMI Sensor Behavior After Host Reboot and Its Impact on Alert Generation in PRTG
In certain operational scenarios—such as power outages, unexpected shutdowns, or unplanned maintenance—it has been observed that when affected devices (particularly Windows-based systems using WMI sensors) are restarted, PRTG successfully restores only basic connectivity sensors (such as Ping), while WMI sensors often fail to resume functionality immediately or automatically.
This behavior results in WMI sensors being unable to establish a connection with the host, triggering errors such as "Connection could not be established". Consequently, the sensor status changes to "Down", which activates notifications configured for genuine operational conditions, such as exceeding CPU, RAM, or disk usage thresholds.
However, this type of alert does not reflect an actual operational issue, but rather a data acquisition failure caused by a disruption in communication between PRTG and the host. Since this condition is not differentiated from a "Down" state due to threshold violation, the alerts are incorrectly routed to operations personnel, generating unnecessary noise and potential misallocation of resources.
Technical Recommendation
It is recommended to evaluate the implementation of logic that distinguishes between:
"Down" state due to threshold violation (actual operational condition).
"Down" state due to data acquisition failure (technical condition).
This would enable:
Redirecting technical alerts to the platform administration team.
Preventing operational alerts from being triggered during host recovery processes.
Improving monitoring accuracy and enhancing incident response efficiency.