Details
-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
Professional Edition
-
Observium 23.11.13173 (14th November 2023)
OS Linux 5.10.0-26-amd64 [amd64] (Debian 11)
Apache 2.4.56 (Debian)
PHP 7.4.33 (OPcache: ENABLED) (Memory: 512MB)
Python 3.9.2
MariaDB 10.5.21-MariaDB-0+deb11u1 (extension: mysqli 7.4.33)
SNMP NET-SNMP 5.9
RRDtool 1.7.2 (rrdcached 1.7.2: unix:/var/run/rrdcached.sock)
Fping 5.0 (IPv4 and IPv6)
Fetch cURL 7.74.0 (OpenSSL/1.1.1w, LibZ 1.2.11, LibIDN 2.3.0)Observium 23.11.13173 (14th November 2023) OS Linux 5.10.0-26-amd64 [amd64] (Debian 11) Apache 2.4.56 (Debian) PHP 7.4.33 (OPcache: ENABLED) (Memory: 512MB) Python 3.9.2 MariaDB 10.5.21-MariaDB-0+deb11u1 (extension: mysqli 7.4.33) SNMP NET-SNMP 5.9 RRDtool 1.7.2 (rrdcached 1.7.2: unix:/var/run/rrdcached.sock) Fping 5.0 (IPv4 and IPv6) Fetch cURL 7.74.0 (OpenSSL/1.1.1w, LibZ 1.2.11, LibIDN 2.3.0)
Description
Dear Observium team,
We, for our own usage, are working on implementing ntfy.sh support for our observium but we have troble working on how to properly integrate it, especialy having trouble understanding how $data is used to and from our transport, how not to push the needed POST in the .inc but to let the notification worker do the job and have it seeing the result as a Sucess, and not as a failed.
We currently have issues with the $data return and seen as a sucess as it currently duplicate the alerts sent.