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

PagerDutty integration issue

Details

    • Bug
    • Resolution: Not A Bug
    • Major
    • None
    • Professional Edition
    • Alerting
    • None

    Description

      Whan we excute this script: ../observium/test_alert.php to test pagerduty alerts the generated curl command is functional, but the call is made in PHP with this code, which fails to make the request using a proxy :

      // Send out API call and parse response
      		 
      for ($retry = 1; $retry <= $request_retry; $retry++) {
      		 
      print_debug("Request #$retry:");
      		 
      if ($notify_status['success'] = test_http_request($transport, get_http_request($url, $options))) {
      		 
      // stop for on success
      		 
      break;
      		 
      }
      		 
      // wait little time
      		 
      sleep($request_sleep);

      We have this responde code :

      RESPONSE CODE[407 Proxy Authentication Required]

      but we don't have authentification on our proxy server

      Attachments

        Activity

          [OBS-4033] PagerDutty integration issue
          Yolf Yassine ATOUI added a comment -

          Hello, issue was internal, everything works well now, sorry for the disturb

          Yolf Yassine ATOUI added a comment - Hello, issue was internal, everything works well now, sorry for the disturb
          landy Mike Stupalov added a comment -

          curl command not used proxy settings..
          How you have configured proxy in config.php?
          Show proxy setttings (with masked passwords).

          landy Mike Stupalov added a comment - curl command not used proxy settings.. How you have configured proxy in config.php? Show proxy setttings (with masked passwords).
          Yolf Yassine ATOUI added a comment -

          Not related to a device descovery issue

          Yolf Yassine ATOUI added a comment - Not related to a device descovery issue
          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
            Yolf Yassine ATOUI
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: