Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • None
    • None

    Description

      Hi!

      After updating to release 21.6.11399 (14th June 2021), notifications via the telegram bot stopped working.

      Empty messages arrive tgbot.png.

       

      When testing sending via the command ./test_alert.php -c 1

      notification come. tgbot2.png

       

      Attachments

        1. tgbot2.PNG
          tgbot2.PNG
          11 kB
        2. tgbot.PNG
          tgbot.PNG
          5 kB
        3. test_alert.txt
          133 kB

        Activity

          [OBS-3796] Empty alerts via telegram bot

          Thank you! It works!

          ori@usla.ru Aleksandr Vedernikov added a comment - Thank you! It works!

          Yah, json with UTF8 (cyrilic) chars.

          Fixed in r11447.
          (Note this is in rolling release).

          landy Mike Stupalov added a comment - Yah, json with UTF8 (cyrilic) chars. Fixed in r11447. (Note this is in rolling release).

          Attached command output
          ./test_alert.php -dd -a 1test_alert.txt

          ori@usla.ru Aleksandr Vedernikov added a comment - Attached command output ./test_alert.php -dd -a 1 test_alert.txt

          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If 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

          Note, this comment is added automatically.

          bot Observium Bot added a comment - Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If 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 Note, this comment is added automatically.

          People

            landy Mike Stupalov
            ori@usla.ru Aleksandr Vedernikov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: