Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-4552

Description field not getting pushed in alerts send via mail or teams webhook, post upgrade

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • None
    • Default
    • None

    Description

      Please help me in one more issue, which happened post upgrade.

       

      description field is not getting sent while alerts are pushed via mail and teams web hook. Please guide, where i can enable description field to be sent.

       

      Entity /Common/DEVEL-POOL
      Description ***this field i am talking about***
      Conditions pool_available equals red (red)
      Metrics pool_available = red

      Attachments

        Activity

          [OBS-4552] Description field not getting pushed in alerts send via mail or teams webhook, post upgrade
          aliasgar215 Aliasgar added a comment -

          Hi Adam,

           

          As i mentioned earlier description were showing up before the upgrade. Even in the alert we have description field, but its not getting polulated. Also we have some dns issues hence we need to go with ip. So please help me with the code to enable description back.

           

          sample of alert added, where it shows description field is blank

          aliasgar215 Aliasgar added a comment - Hi Adam,   As i mentioned earlier description were showing up before the upgrade. Even in the alert we have description field, but its not getting polulated. Also we have some dns issues hence we need to go with ip. So please help me with the code to enable description back.   sample of alert added, where it shows description field is blank
          adama Adam Armstrong added a comment -

          Observium is not intended to have devices added by IP address. If you add devices by hostname, the hostname will be displayed in alerts.

          Alert notifications have very restricted character length, and generally don't show the entity description.

          adama Adam Armstrong added a comment - Observium is not intended to have devices added by IP address. If you add devices by hostname, the hostname will be displayed in alerts. Alert notifications have very restricted character length, and generally don't show the entity description.
          aliasgar215 Aliasgar added a comment -

          actually we have hostname mentioned in the description which is require to identify the device, just with the ip its not feasible to understand which device is giving alert. hence please help me with the setting to enable description field in the alert via teams webhook and mail.

          aliasgar215 Aliasgar added a comment - actually we have hostname mentioned in the description which is require to identify the device, just with the ip its not feasible to understand which device is giving alert. hence please help me with the setting to enable description field in the alert via teams webhook and mail.
          aliasgar215 Aliasgar added a comment -

          yes, please help me with the setting to enable it back.

          aliasgar215 Aliasgar added a comment - yes, please help me with the setting to enable it back.
          adama Adam Armstrong added a comment -

          Are you sure this happened post upgrade? We generally don’t send description fields with alerts because they’re too long.

          adama Adam Armstrong added a comment - Are you sure this happened post upgrade? We generally don’t send description fields with alerts because they’re too long.
          bot Observium Bot added a comment -

          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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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

          This comment is added automatically.

          bot Observium Bot added a comment - 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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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 This comment is added automatically.

          People

            landy Mike Stupalov
            aliasgar215 Aliasgar
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: