Hello.

I tested this notice and not working.

Enter the URL in the browser and I get an error http 400

I simply replaced the ip of the server, the number of sensor and the user.

What am I doing wrong?

Thanks

Hello, have you checked if your PRTG web interface uses http or https?

Note: Please make sure that no Proxy is involved here that could 'redirect' the HTTP Request from the PRTG Core to something else not PRTG itself

Auto-Acknowledge Setting for Ping Sensor

As of PRTG version 9, the Ping sensor has an option to automatically acknowledge alarms.

For more information, please see PRTG Manual: Ping Sensor (search for "Auto Acknowledge")

This still works in PRTG 12. I've Just set it up and got it running. I have a whole bunch of devices that people turn-off at night is the best solution. (pausing them at night robs us of too much data)

Note: Please make sure that no Proxy is involved here that could 'redirect' the HTTP Request from the PRTG Core to something else not PRTG itself

-> Is there a way to work with that auto-acknow. if I am using a proxy with user-auth. ?

Afraid not, sorry.

Hi, I'm using PRTG version 13. I have a HTTP sensor and have tried following the instructions given above:

Choose a sensor you want to set up auto-acknowledging for. On the sensor's detail page, click on the Notifications tab. Click on Add State trigger and add a notification for a Down Condition and with the On Notification "Auto-Acknowledge Sensor Down". Click on Save.

I do not have an option for "Auto-Acknowledge Sensor Down", all I can see are a list of the notification groups we have set up ourselves.

Any guidance would be appreciated.

Thanks

Dear Emma

Before you can use a HTTP transaction to autoacknowledge a sensor, please create the HTTP URL as described in step 1.

This URL needs to be entered in the respective notification to perform the API call to acknowledge. Beside "ping", sensor settings have no build-in option for autoacknowledge, that is why the HTTP URL for the API call needs to be created first.

Hello Paessler Team,

I must ask this :) we have the situation, that we have 2 Windows Machines which work as a manual active/standby Cluster the respective Service is only on one machine at a time active.

We check via SNMP the state of the Sensor. On One Machine it is obiously not available so we have an Error.

Therefor I would like to auto ack this. Unfortunately we have a Proxy Environment to everything outside our Domain. I tried now several requests in the http action notification:

https://host.domain/api/acknowledgealarm.htm?id=%sensorid&ackmsg=Auto-Acknowledged&username=user&passhash=123 https://host/api/acknowledgealarm.htm?id=%sensorid&ackmsg=Auto-Acknowledged&username=user&passhash=123 https://IP-address/api/acknowledgealarm.htm?id=%sensorid&ackmsg=Auto-Acknowledged&username=user&passhash=123 https://localhost/api/acknowledgealarm.htm?id=%sensorid&ackmsg=Auto-Acknowledged&username=user&passhash=123 https://127.0.0.1/api/acknowledgealarm.htm?id=%sensorid&ackmsg=Auto-Acknowledged&username=user&passhash=123

so it thems that it does not work, If I enter the API Calls via a Browser it is working like a charm. since a Proxy is mandatory between the domain network and the internet it is no solution to disable it on the core. Also the Proxy definition via our Proxy.pac say that local destinations should not go via our Proxy. Unfortunately it seems that they go towards the proxy :(

is there any other way to do this?

Dear Michele

If you have troubles circumventing the proxy, the only solution would be to call a program instead, like a powershell script, which then invokes the HTTP action.

Please note that this solution is overall so complex that we don't recommend it.

Hello again,

PowerShell Script was also my last point of hope and yeah it was not as complicated as expected. I could share it here of course

just need to change the User and the passhash with your credentials at the URI build part

##
# params
# Sensorid via PRTG variable: %sensorid
# AckMessage to Display in Sensor Last Message field
##
param
(    
    [string]$SensorID,
    [string]$AckMessage
)

##
# Bypass Cert Issue
# This is not coded by me, please find the source below
# Source: http://grumpyneteng.com/powershell-httpsssl-and-self-signed-certificates/
##
Add-Type @"
    using System;
    using System.Net;
    using System.Net.Security;
    using System.Security.Cryptography.X509Certificates;
    public class ServerCertificateValidationCallback
    {
        public static void Ignore()
        {
            ServicePointManager.ServerCertificateValidationCallback += 
                delegate
                (
                    Object obj, 
                    X509Certificate certificate, 
                    X509Chain chain, 
                    SslPolicyErrors errors
                )
                {
                    return true;
                };
        }
    }
"@
[ServerCertificateValidationCallback]::Ignore();

##
# Build URI variable String with Param
##
$URI="https://127.0.0.1/api/acknowledgealarm.htm?id=$SensorID&ackmsg=$AckMessage&username=<APIUserA>&passhash=<PASSHASH>"

##
# enter PRTG API call to Auto-Ack the down sensor
##
Invoke-RestMethod -Method GET -Uri $URI

afterwards just add a Execute Program notification with this program file and as parameters %sensorid YourAckMessage

is it possible to autoacknowledge an Sensor for x minutes with that API call?

Dear Michel

You can acknowledge a sensor with a API call, but not auto-acknowledge it:

/api/acknowledgealarm.htm?id=<id>&ackmsg=Message&duration=15

An option would be to run such API call as HTTP action as part of a notification, meaning as sensor will (always) acknowledge itself.

I've had the "Auto-Acknowledge Sensor Down" HTTP Notification working for quite some time but it seems to have broken with the 22.3.78.1873. Nothing has changed besides the PRGT version. I've tried HTTP and HTTPS and confirmed PRTG username and passhash are correct.

Here's the log:

Failed to establish secure connection [Step 0] Socket Error # 10061 Connection refused. [Step 1] Socket Error # 10061 Connection refused. [Step 2] Socket Error # 10061 Connection refused. [Step 3] Socket Error # 10061 Connection refused. [Step 4] Socket Error # 10061 Connection refused. [Step 5] Socket Error # 10061 Connection refused. [Unsecure] IOHandler value is not valid

Hello Dave,

which log exactly is that? I ask because there are multiple components in PRTG which could show such output.

Also, does the API call work if you perform in manually (like, in a browser) or is there no effect, either?