Ad Widget

Collapse

New macro SERVICE.STARTUPTRIGGER

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mbrackeva
    Junior Member
    • Feb 2016
    • 27

    #1

    New macro SERVICE.STARTUPTRIGGER

    I'm trying to get this to work. I want to discover all Windows services with state Automatic, but not the ones with startup trigger. According to the documentation this can be done, since 3.4.4, by using the new macro SERVICE.STARTUPTRIGGER. I tried to add that to the discovery rule's filters ({#SERVICE.STARTUPTRIGGER} = 0), but all Windows services now disappear from the LLD!
    Am I doing something wrong?
    Attached Files
  • mbrackeva
    Junior Member
    • Feb 2016
    • 27

    #2
    I'm using a 3.4.0 agent instead of 3.4.4 or higher. Can it be that this feature required a change in the agent as well? In that case, our current setup can't work...

    Comment

    • kaspars.mednis
      Senior Member
      Zabbix Certified Trainer
      Zabbix Certified SpecialistZabbix Certified Professional
      • Oct 2017
      • 349

      #3
      Hi,

      Windows service LLDs are done by zabbix agent on the host, so it seems logic to me that old agents are not supporting this new functionality. You can try to test it with just one host with upgraded agent...

      Regards,
      Kaspars

      Comment

      Working...