JEC Zabbix Integration / Acknowledge of Events in Zabbix if Alert is Acknowledged

[Daniel Hestermann]

Hello everyone,

we are trying to configure the jec plugin to manipulate Zabbix Events if the Alert in JSM is altered.

Especially currently trying to pass the information of acknowledged Alerts to Zabbix is not working.

We see in the jec logs that the messages ist received by the Zabbix plugin but it´s not processed due to a problem.

This is the log we see in JEC on the Zabbix server:

INFO[2025-08-25T12:26:32.057513383+02:00] JEC version is 1.0.5
INFO[2025-08-25T12:26:32.05768228+02:00] JEC commit version is 33a5bc184f248344c4763b21173aa7e56606f831
INFO[2025-08-25T12:26:32.057952253+02:00] Visibility timeout cannot be lesser than 15 seconds or
greater than 12 hours, default value[30 s.] is set.
INFO[2025-08-25T12:26:32.058105762+02:00] JEC-metrics serves in http://localhost:7070/metrics.
INFO[2025-08-25T12:26:32.058145944+02:00] Queue processor is starting.
INFO[2025-08-25T12:26:32.715499787+02:00] Worker pool has started to run.
INFO[2025-08-25T12:26:32.715557201+02:00] Worker pool is running with; Min Worker: 4, Max Worker: 12, Queue Size: 0
DEBUG[2025-08-25T12:26:32.715610094+02:00] worker[bd178c58-1fd5-460a-8eb3-27a3519fa160] is spawned.
INFO[2025-08-25T12:26:32.715644168+02:00] Poller[https://sqs.us-west-2.amazonaws.com/089311581210/jec_f3f796e3-6fcd-41b7-bca7-ed81d5de6c65_2666d0bc-38f8-4eff-8247-26951051dda3] has started to run.
DEBUG[2025-08-25T12:26:32.715632054+02:00] Poller[https://sqs.us-west-2.amazonaws.com/089311581210/jec_f3f796e3-6fcd-41b7-bca7-ed81d5de6c65_2666d0bc-38f8-4eff-8247-26951051dda3] is added.
DEBUG[2025-08-25T12:26:32.715519251+02:00] worker[4bf1b848-cf5a-4869-8f32-aea38b55c575] is spawned.
INFO[2025-08-25T12:26:32.715748767+02:00] Queue processor has started to run. Refresh client period: 1m0s.
DEBUG[2025-08-25T12:26:32.715531167+02:00] worker[34af5999-148d-4c43-b8c9-4b8668fd0ae4] is spawned.
DEBUG[2025-08-25T12:26:32.715536909+02:00] worker[74a99880-7a2d-4d36-8ab4-28b9302bb28a] is spawned.
DEBUG[2025-08-25T12:26:47.718253463+02:00] Current Worker: 4, Idle Worker: 4, Queue Size: 0, Queue load: 0
DEBUG[2025-08-25T12:26:54.842514207+02:00] Received 1 messages from the queue[us-west-2].
DEBUG[2025-08-25T12:26:54.842611373+02:00] Job[a68c7218-6637-4bcb-94f3-8872e532dd48] is being submitted
DEBUG[2025-08-25T12:26:54.842725216+02:00] Job[a68c7218-6637-4bcb-94f3-8872e532dd48] is submitted to worker[4bf1b848-cf5a-4869-8f32-aea38b55c575]
DEBUG[2025-08-25T12:26:55.508991413+02:00] Message[a68c7218-6637-4bcb-94f3-8872e532dd48] is deleted from the queue[us-west-2].
DEBUG[2025-08-25T12:26:55.509194126+02:00] Could not create named pipe with name /var/tmp/jec/jecCallbackPipe-a68c7218-6637-4bcb-94f3-8872e532dd48. Error: permission denied
DEBUG[2025-08-25T12:26:55.509266173+02:00] Could not open named pipe. Error: open /var/tmp/jec/jecCallbackPipe-a68c7218-6637-4bcb-94f3-8872e532dd48: no such file or directory
DEBUG[2025-08-25T12:26:55.509298332+02:00] Error reading from the named pipe:invalid argument
DEBUG[2025-08-25T12:26:55.509309174+02:00] Could not delete named pipe /var/tmp/jec/jecCallbackPipe-a68c7218-6637-4bcb-94f3-8872e532dd48
DEBUG[2025-08-25T12:26:55.509269013+02:00] Could not open named pipe to write default callback context
DEBUG[2025-08-25T12:26:55.509331609+02:00] Could not write to named pipe
DEBUG[2025-08-25T12:26:55.50935064+02:00] Action[Acknowledge] execution of message[a68c7218-6637-4bcb-94f3-8872e532dd48] failed: exec: "python": executable file not found in $PATH Stderr:
DEBUG[2025-08-25T12:26:55.509380019+02:00] Job[a68c7218-6637-4bcb-94f3-8872e532dd48] has been processed by worker[4bf1b848-cf5a-4869-8f32-aea38b55c575].
DEBUG[2025-08-25T12:26:56.159486669+02:00] Successfully sent result of message[a68c7218-6637-4bcb-94f3-8872e532dd48] to Jira Service Management and it took 0.650070 seconds.
DEBUG[2025-08-25T12:27:02.716684034+02:00] Current Worker: 4, Idle Worker: 4, Queue Size: 0, Queue load: 0