Ad Widget

Collapse

Basic Trigger to alert on service status

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rn21528nr
    Junior Member
    • Jul 2022
    • 13

    #1

    Basic Trigger to alert on service status

    Hello,
    Im already using the built in Windows Services template, however i want to make a customer trigger that is higher severity for a certain service. The item data "state of service myservice" already exists for all of my hosts, but im having trouble referencing this item from a custom trigger. It seems like i can create this trigger for one particular host, but i'm trying to make it for the entire template, like this:

    last(/Windows services by Zabbix agent active/service.info["MyService",state])=0

    I can only find that item if i create the trigger using one host, like this : last(/myhostname/service.info["myService",state])=0

    What am i doing wrong?
  • Markku
    Senior Member
    Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
    • Sep 2018
    • 1781

    #2
    I don't have experience on this on my own, but I'm pretty sure you can use LLD overrides for this (= modify the severity of a trigger that gets created by LLD). So, see the Overrides tab on the service discovery rule in the template.

    Markku

    Comment


    • rn21528nr
      rn21528nr commented
      Editing a comment
      ok i tried this and it didn't work (unless i configured it wrong). The alerts are still coming with the normal (orange) severity. Heres what i tried : In LLD -Overrides i created an override with "Filter: {#service.name} matches myServiceName" , "Operation: Trigger prototype equals is not running" . I also set the severity = high.
  • Markku
    Senior Member
    Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
    • Sep 2018
    • 1781

    #3
    Did you use {#service.name} or {#SERVICE.NAME}?

    Did you delete the old trigger (on the host) first?

    Did you ensure that the discovery was executed without errors?

    Markku

    Comment


    • rn21528nr
      rn21528nr commented
      Editing a comment
      ok so i got this working after some tinkering (still not 100% sure what did it... maybe deleting the old discovered trigger for that svc? Maybe it was checking the "discover" checkbox? or the "create enabled checkbox?". Any way, for my existing hosts that already have that trigger in place, do i need to manually delete the trigger for every host? Is there a better way of doing this? Thanks
  • Markku
    Senior Member
    Zabbix Certified SpecialistZabbix Certified ProfessionalZabbix Certified Expert
    • Sep 2018
    • 1781

    #4
    My understanding it that you need to delete the old trigger because the discovery won't update the existing triggers (because it cannot know if you have manually edited them in purpose). You have now lots of material to test it, right? So report back how it went (preferably using reply and not comment, as comment cannot be "liked" or quoted easily).

    Note that in the triggers configuration list you can show the same item from multiple hosts at once by filtering by host group and then entering the trigger name in the Name field. That way it is easy to delete all relevant triggers at once.

    Markku

    Comment

    Working...