Ad Widget

Collapse

Zabbix web api trigger can't be added in a template which is linked to another one

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • elendrys
    Junior Member
    • Oct 2019
    • 2

    #1

    Zabbix web api trigger can't be added in a template which is linked to another one

    Hello,

    I configured in Zabbix 4.0 a set of templates which monitor APIs. Each on has one or more Web scenario and some triggers when they fail (web.test.fail or web.test.time). I then created another template in which I linked all the previous one. I can then associate the main template to a new host and all the APIs are monitored.

    We upgraded to 4.2 and after some struggle exporting/reimporting from preprod to prod, I'm stuck with these triggers. Whenever I try to link template A/B/C with the scenarios and triggers to the main template I have the error :
    Cannot add trigger
    • Incorrect item key "web.test.fail['Api: Cinder']" provided for trigger expression on "Template Openstack Controller Openstack Services".
    I tried to link the template before reconfiguring these triggers but the same error pops up.

    Is it a bug or do I misconfigure Zabbix ? It was successfully setup in 4.0

    Thank you
    elendrys
  • elendrys
    Junior Member
    • Oct 2019
    • 2

    #2
    Thank you so much for all these answers. Zabbix is such a great product \0/ that it can't manage quotes between its modules.

    This shit is happening:
    - export a template
    - import fails for web.test.fail and web.test.time with error "incorrect key name"
    - edit the template export and surround scenario name with quotes
    - import succeed
    - link concerned templates within another one fails with the same error
    - edit all scenarios with doing nothing but clicking update
    - linking works

    No quotes in the exported template. What happens ?

    Wow no need to ask -> no answers given in 6 months

    Comment

    • dimir
      Zabbix developer
      • Apr 2011
      • 1080

      #3
      What 4.2.X version exactly are you running? Do I understand correctly that you were copying 4.0 templates to 4.2?

      Thing is, 4.2 is not supported version any more. You should consider upgrading to 5.0 as it will be LTS. Currently it's beta1 so first release candidate is not far away.
      Last edited by dimir; 17-04-2020, 15:58.

      Comment

      Working...