[ZBX-21707] zabbix 6.0 -> GLPI 10.x : resolve sync issue Created: 2022 Sep 29  Updated: 2024 Apr 10  Resolved: 2022 Oct 04

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 6.0.8, 6.0.9, 6.2.2, 6.2.3
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Guillaume Roth Assignee: Evgenii Gordymov
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 20.04 LTS

Attachments: PNG File Capture d’écran 2022-09-29 à 11.35.30.png     PNG File Capture d’écran 2022-09-29 à 11.35.47.png     PNG File Capture d’écran 2022-09-29 à 11.36.18.png     PNG File Capture d’écran 2022-09-29 à 11.37.23.png     PNG File Capture d’écran 2022-09-29 à 11.41.37.png     PNG File Capture d’écran 2022-09-29 à 11.44.02.png     PNG File Capture d’écran 2022-09-29 à 11.44.27.png     PNG File Capture d’écran 2022-09-29 à 11.44.37.png     PNG File Capture d’écran 2022-09-29 à 11.45.12.png    
Team: Team INT
Story Points: 2

 Description   

Steps to reproduce:

  1. insctructions notes provided by Zabbix : https://www.zabbix.com/integrations/glpi
  2. create a dedicated Profil " monitoring " in GLPI, dedicated user " zabbix " in GLPI.
  3. in Zabbix, i create a Trigger test.
  4. Trigger action is setup as the screenshots shows

Result:

When a problem appears in zabbix, the system create a problem in GLPI

When this problem is solved in zabbix, GLPI webhook is showing this message " Sending failed: Recovery operations are supported only for trigger-based actions. "

 Comments   
Comment by Evgenii Gordymov [ 2022 Oct 03 ]

Hello, gu1llohm. 
Can you change parameter 'event_source' --> {EVENT.SOURCE} and test it again.

I see number "2" in 'event_source' field on your screenshot.

Comment by Guillaume Roth [ 2022 Oct 03 ]

You are completely right ! 

i was that. 

Many thanks for your help.. sometime details are front of us.. 

Thanks for your amazing job !! 

 

G.

Generated at Tue Apr 15 17:18:10 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.