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

MSTeams contact webhook not work

Details

    • Help
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Alerting
    • None

    Description

      Hello,

      we have problems with MSTeams webhook contact, notifications not come to our MS Teams channel.

      We test it also with test_alert.php and we get response status: 400

      ./test_alert.php -d -c 2

      REQUESThttps://XXXX.webhook.office.com/webhookb2/XXXXX/IncomingWebhook/XXXXX
      REQUEST STATUS[FALSE]
      REQUEST RUNTIME[0.5199s]
      RESPONSE CODE[400 Bad Request]

      RESPONSE STATUS[400]
      RESPONSE ERROR[Summary or Text is required.]

       

      Thank you and best regards.

      Attachments

        Activity

          [OBS-4061] MSTeams contact webhook not work
          rok.skufca@epilog.net Rok added a comment -

          Arrr...sory for that...yes it works with "Microsoft Teams".

           

          Thank you for your support, you can close issue.

          rok.skufca@epilog.net Rok added a comment - Arrr...sory for that...yes it works with "Microsoft Teams".   Thank you for your support, you can close issue.
          adama Adam Armstrong added a comment -

          Webhooks from different vendors won't talk to eachother. The Observium webhook is specific to Observium and is intended for people to write code especially to talk to Observium.

          The MS Teams webhook is specific to MS Teams and is intended for people to write code especially to talk to MS Teams.

          These two webhooks can't talk to eachother.

          To send notifications to Teams you need to use the "Microsoft Teams" transport, present in Pro and Enterprise versions.

          adama Adam Armstrong added a comment - Webhooks from different vendors won't talk to eachother. The Observium webhook is specific to Observium and is intended for people to write code especially to talk to Observium. The MS Teams webhook is specific to MS Teams and is intended for people to write code especially to talk to MS Teams. These two webhooks can't talk to eachother. To send notifications to Teams you need to use the "Microsoft Teams" transport, present in Pro and Enterprise versions.
          rok.skufca@epilog.net Rok added a comment -

          rok.skufca@epilog.net Rok added a comment -
          landy Mike Stupalov added a comment -

          Please show contact settings screenshot (hide webhook url).

          landy Mike Stupalov added a comment - Please show contact settings screenshot (hide webhook url).
          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 -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --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

          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 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --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 This comment is added automatically.

          People

            adama Adam Armstrong
            rok.skufca@epilog.net Rok
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: