Ad Widget

Collapse

Help with Web Scenario Triggers!

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • enkrypt3d
    Member
    • Oct 2013
    • 32

    #31
    Originally posted by MaxM
    Instead of playing the 'guessing game', why not just click the add button and find the item and have zabbix populate the key for you?
    Its not listed - as you can see earlier in this thread its a "hidden" item key.... no matter which hidden one I try it says its invalid.

    Comment

    • MaxM
      Member
      • Sep 2011
      • 42

      #32
      Originally posted by enkrypt3d
      Its not listed - as you can see earlier in this thread its a "hidden" item key.... no matter which hidden one I try it says its invalid.
      It won't be listed as an item when you go to items (as they are web items... which is annoying, they really should show as unmodifable items and be treated as such... but that's a digression for another time), but every single web item shows when I go through Configuration > Template > ${TemplateName} > Triggers > Create Trigger > Add > Select (item). I immediately see a list of the web items and any other items in the template.

      Comment

      • enkrypt3d
        Member
        • Oct 2013
        • 32

        #33
        Originally posted by MaxM
        It won't be listed as an item when you go to items (as they are web items... which is annoying, they really should show as unmodifable items and be treated as such... but that's a digression for another time), but every single web item shows when I go through Configuration > Template > ${TemplateName} > Triggers > Create Trigger > Add > Select (item). I immediately see a list of the web items and any other items in the template.
        Wow.... I can't believe it actually worked! Why are these triggers buried?

        They should be displayed along with all the other items and triggers...

        So how would I use this in a template for hosts that have different external DNS names? {HOST.DNS} ? Update: This doesn't work either)

        Because when I create the trigger in the template, I have to choose one host that has that trigger in the trigger expression:

        {specifichostname.com:web.test.fail[Heath Check].last()}=0

        After I create this trigger, it still does not show up in the list of triggers that are associated with the template.... Why would this be a "feature" to hide this?

        This means that using templates is useless. Because the above trigger expression is tied to a specific hostname and can not be used in a template.

        UPDATE: The only way that I was able to get this to "work" was outside of a template...

        Create the web scenario, go to templates > triggers > create trigger > Add expression >

        Select Item (I dont get why these items doesn't show up anywhere else!??!) >

        Then select a host in the drop down menu (You have to choose a server that will be checked - This again is another clunky part that would be avoided if the items showed up in the template) >

        Choose some function (which one for last failed step?) > Click Save

        Go to host that has new *HIDDEN* trigger > Select it and copy it to a host group.

        This makes absolutely no sense why this isn't treated like every other item / trigger in zabbix...

        Even when you go back to try and create this trigger inside a template, the new trigger never shows up in the template. There is no item either. Also there is no rhyme or reason as far as the relationship between web scenarios and its triggers.
        Last edited by enkrypt3d; 13-12-2013, 02:18.

        Comment

        • enkrypt3d
          Member
          • Oct 2013
          • 32

          #34
          Bumping this thread... I updated to 2.2.1 but I doubt this has any patches to the web scenario handling....

          Can anyone advise as to why the triggers are not showing up in the template even after I create them manually?

          Comment

          • MaxM
            Member
            • Sep 2011
            • 42

            #35
            Originally posted by enkrypt3d
            So how would I use this in a template for hosts that have different external DNS names? {HOST.DNS} ? Update: This doesn't work either)

            Because when I create the trigger in the template, I have to choose one host that has that trigger in the trigger expression:

            {specifichostname.com:web.test.fail[Heath Check].last()}=0

            After I create this trigger, it still does not show up in the list of triggers that are associated with the template.... Why would this be a "feature" to hide this?
            It sounds like you're associating the trigger with a specific host, instead of the template itself. Once you get into the 'pick and choose an item' pop-up, make sure to select templates from the drop down for groups, then your template from the host drop down. That should then populate the trigger at the template level, which will mean the host part of the key will get auto-mapped. I've been able to do this successfully with 15 Web Templates. The trigger isn't 'hidden' or anything like that.
            Attached Files

            Comment

            • enkrypt3d
              Member
              • Oct 2013
              • 32

              #36
              That's what I was doing - I was trying to add the trigger to an existing template but I guess it doesn't like that.

              FINALLY got this working. It's convoluted but it works.

              The web scenario triggers can check status codes (200 etc) or strings or both. For redundancy I have it checking for a 200 and the string.

              Basically I had to create a new zabbix template for the external checks I want to monitor. Then create the web scenario from within that template which assigns each web check to the hosts that are in that template with the URL like this:

              Example web scenario URL check:
              http://{HOST.NAME}/health.jsp

              Return code: 200 string: OK

              Once the web scenario is created, you create the trigger you want:

              {MP32 Servers:web.test.fail[MP32 Health Check].change(0)}#0

              MP32 Servers is the name of the template and MP32 Health Check is the name of the web scenario.

              I spent a solid week on figuring this out. This seriously should not be this difficult.

              Comment

              Working...