Cannot see the snmp-server trap output

[bmgante]

What did you do? Send alert using curl to snmp-notifier and this one sending trap to snmp-server, both running in EKS. SNMP-Notifier installed using helm and snmp-server deploying the manifest available under scripts/kubernetes.

What did you expect to see? I was expecting to see the trap output in snmp-server stdout.

What did you see instead? Under which circumstances? The snmp-notifier receives the alert and with 200OK but i am not able to see anything on the snmp-server stdout.

Environment

• System information:

  EKS

• SNMP notifier version:

  1.5.0

• Alertmanager version:

  N/A

• Prometheus version:

  N/A

• Alertmanager simulated post:

  curl -i -H "Host: alertmanager-snmp-notifier:9464" -H "User-Agent: Alertmanager/0.23.0" -H "Content-Type: application/json" --request POST --data @alert1_warning_resolved.json http://alertmanager-snmp-notifier.network-observability.svc.cluster.local:9464/alerts
  HTTP/1.1 200 OK
  date: Mon, 05 Feb 2024 13:25:44 GMT
  content-length: 0
  x-envoy-upstream-service-time: 1
  server: envoy

alert1_warning_resolved.json:

{
  "receiver": "snmp-notifier",
  "status": "firing",
  "groupLabels": {
    "environment": "staging",
    "label": "test"
  },
  "alerts": [
    {
      "status": "firing",
      "labels": {
        "severity": "warning",
        "alertname": "TestAlert1"
      },
      "annotations": {
        "message": "this is the message of alert 1"
      }
    }
  ]
}

• SNMP-Notifer logs:

  k logs -f alertmanager-snmp-notifier-5f5446bbdc-cmb9z
  ts=2024-02-05T13:13:11.430Z caller=snmp_notifier.go:40 level=debug configuration="unsupported value type"
  ts=2024-02-05T13:13:11.431Z caller=tls_config.go:274 level=info msg="Listening on" address=[::]:9464
  ts=2024-02-05T13:13:11.431Z caller=tls_config.go:277 level=info msg="TLS is disabled." http2=false address=[::]:9464
  ts=2024-02-05T13:17:41.035Z caller=http_server.go:79 level=debug msg="Handling /alerts webhook request"

• snmp-server logs:

  
  k logs -f snmp-server-546f65b5d6-bvgxg
  NET-SNMP version 5.9.3

/var/lib/zabbix/snmptraps $ ps -ef PID USER TIME COMMAND 1 zabbix 0:00 /usr/sbin/snmptrapd -n -C -c /etc/snmp/snmptrapd.conf -Lo -A 24 zabbix 0:00 /bin/sh 33 zabbix 0:00 ps -ef

[bmgante]

The problem was the config for the snmp-server, i was using the default SNMPv2c on the snmp-notifier while the snmp-server config was set to snmpv3. Did the following changes

  snmptrapd.conf: |
    # A list of listening addresses, on which to receive incoming SNMP notifications
    snmpTrapdAddr udp:1162
    snmpTrapdAddr udp6:1162

    # Do not fork from the calling shell
    doNotFork yes
    # File in which to store the process ID of the notification receiver
    pidFile /tmp/snmptrapd.pid
    # Disables support for the NOTIFICATION-LOG-MIB
    doNotRetainNotificationLogs yes

    # Format of the trap output for SNMPv3
    # format2 %V\n% Agent Address: %A \n Agent Hostname: %B \n Date: %H - %J - %K - %L - %M - %Y \n Enterprise OID: %N \n Trap Type: %W \n Trap Sub-Type: %q \n Community/Infosec Context: %P \n Uptime: %T \n Description: %W \n PDU Attribute/Value Pair Array:\n%v \n -------------- \n

    # Format of the trap output for SNMPv2c
    format2 %B[%A]: %W-%q - %P - %U - %v\n

    #SNMPv3
    #createUser -e 0x8000000001020304 snmp_user_v3 SHA auth_password_v3 AES encrypt_password_v3

    #SNMPV3
    # authUser log,execute,net snmp_user_v3

    authCommunity log,execute,net public

[maxwo]

Thanks for your feedback. I can now close this issue. Thank you