Settings and activity
89 results found
-
13 votes
Viswanathan Ramanathan supported this idea ·
-
15 votes
An error occurred while saving the comment Viswanathan Ramanathan supported this idea ·
-
21 votes
Viswanathan Ramanathan supported this idea ·
-
3 votes
Viswanathan Ramanathan supported this idea ·
-
6 votes
Viswanathan Ramanathan supported this idea ·
-
6 votes
Viswanathan Ramanathan supported this idea ·
-
5 votes
Viswanathan Ramanathan supported this idea ·
-
12 votes
Viswanathan Ramanathan supported this idea ·
-
26 votes
An error occurred while saving the comment Viswanathan Ramanathan commented
We are facing lots of monitoring issues as new Windows Servers require Kerberos authentication and the WMI sensors fail. Enabling this will help us resolve this.
Viswanathan Ramanathan supported this idea ·
I face this issue all the time, where sensors are down due to data fetching issues. The tickets that are created get assigned to the Operations Team, who then check the devices and report that everything is normal and close the ticket with an incorrect resolution. These tickets should ideally be assigned to the Tools Team who can then take necessary steps to rectify the error and resume proper monitoring. So treating “Down” and “Error” as different states in PRTG will help with:
1. Faster triage
2. Root-cause isolation
3. Correct escalation
4. SLA accuracy (Availability vs. Monitoring health)
5. Cleaner dashboards & executive KPIs
6. Better auto-remediation
7. Noise reduction & alert deduplication
8. Clean alerting
9. Reliable reporting