Open joschi99 opened 4 months ago
Hello :)
According to my research, it seems that the error management is not internal to the plugin itself but managed by the JSON::XS library and it is when it returns an error when decoding a JSON that the plugin returns the output Cannot decode response
. It should therefore be possible to offer filtering on certain error(s) via an option. For this it would be necessary to generate test data in your conditions on which we could work to implement this option.
I send you here the complete json output:
[centreon-engine@srv-mou-poller ~]$ speedtest -f json
{"type":"log","timestamp":"2024-08-30T07:30:48Z","message":"Error: [0] Timeout occurred in connect.","level":"error"}
{"type":"result","timestamp":"2024-08-30T07:31:07Z","ping":{"jitter":0.065,"latency":1.057,"low":1.001,"high":1.146},"download":{"bandwidth":48121220,"bytes":592859280,"elapsed":12509,"latency":{"iqm":1.869,"low":1.009,"high":218.068,"jitter":9.665}},"upload":{"bandwidth":116247898,"bytes":686240420,"elapsed":5925,"latency":{"iqm":2.507,"low":1.478,"high":25.679,"jitter":1.464}},"packetLoss":0,"isp":"Optimum WiFi","interface":{"internalIp":"192.168.218.40","name":"ens192","macAddr":"00:50:56:87:1F:B2","isVpn":false,"externalIp":"65.51.128.50"},"server":{"id":62092,"host":"speedtest02.srv.prnynj.alticeusa.net","port":8080,"name":"Optimum Online","location":"Parsippany, NJ","country":"United States","ip":"148.76.236.58"},"result":{"id":"9c3b54fc-b176-4154-b6c7-af88d672dddd","url":"https://www.speedtest.net/result/c/9c3b54fc-b176-4154-b6c7-af88d672dddd","persisted":true}}
speedtest cli returns timeout and this will probably create the problem. every port for speedtest is open, we are not able to understand why we have this timeout on speedtest cli
Hello :)
Thanks for the test data. We'll see what we can do about it.
Latest plugins
If we launch the speedtest manualy we will have this output:
As you can see the speedtest by self is working but we have the exception
[error] Error: [0] Cannot read from socket:
wich probably will cause the problem. Could you ignore this exception in the plugin?