Major Description
If kannel is in queue at first place and it fails request, then after that in queue is Webhooks request it fails too.
Kannel is not reached its true, but it must have succesfully reach out Webhooks.
curl --connect-timeout 15 -X GET -H 'Connection: close' -H 'User-Agent: Observium/22.10.12332' https://kannel.&text=[text]
get_http_request() exit with timeout. Access to outside localnet is blocked by firewall or network problems. Check proxy settings.
Rocketchat is reached by the server, but Observium ignores the fact that Rocketchat is working and if first the HTTP request failed the second one is failed too.
rocketchat-hook
Use definition based notification transport
Definition message template file is used.
Request #1:
HTTP requests skipped since previous request exit with timeout
REQUEST STATUS[FALSE]
RESPONSE CODE[408 Request Timeout]
[FALSE]
Attachments
Activity
Hello Mike,
The problem is not with Kannel, the problem is with Webhooks.
Example:
Contact List
Transport = e-mail; Description = username A; Destination = username@mail (send succefully)
Transport = Kannel SMS; Description = username A; Destination = phone username A (sending fails)
Transport = WebHook (Rocket.chat / Slack); Description = Chatname; Destination = URL (If Kannel IS FAILED, Webhook FAILS TOO)
Transport = e-mail; Description = username B; Destination = usernameB@mail (send succefully)
Is it normal behavior? Both Kannel and WeebHooks are using HTTPS for a transport.
Please make debug notification tests (and attach it or send me to mike@observium.org), for kannel and Rocketchat contacts as:
./test_alert.php -d -c <contact_id>
|
where contact_id is number associated with specific transport.
P.S. Note, curl command showed only for debug purposes.
General questions and device support can be discussed in our Discord channel, click here to join.
Please make and attach additional information about the device:
- full snmp dump from device:
snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalksnmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalkIf device not support SNMP version 2c, replace -v2c with -v1.
- If you have problems with discovery or poller processes, please do and attach these debugs:
./discovery.php -d -h <device>./poller.php -d -h <device>
- additionally attach device and/or vendor specific MIB files
This comment is added automatically.
Ok, now understand. Should be fixed in r12380.