Ad Widget

Collapse

Monitoring remote Windows service

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • fossiel
    Junior Member
    • Jan 2012
    • 14

    #16
    Monitoring remote Windows service

    OK made all the hosts from scratch.
    Open tcp AND udp on the firewall, think this is not the solution.
    Found on the forum:


    Did this:
    SuSEfirewall2 open EXT TCP zabbix-trapper zabbix-agent

    Then reload the firewall rules:

    SuSEfirewall2 stop
    SuSEfirewall2 start
    and now the data is coming in!!!.
    So I have the correct data qua memory host info etc.
    But the trigger on the service is not working.

    Comment

    • fossiel
      Junior Member
      • Jan 2012
      • 14

      #17
      Monitoring remote Windows service

      OK data is coming in except the spooler status.
      Done:
      zabbix_sender -z <Myfirewallip> -p 10051 -s <remote server ip> -i 0.0.0.0 -k service_state[Spooler]

      Now the spooler data is coming in too:
      Click image for larger version

Name:	Some-data.jpg
Views:	1
Size:	11.2 KB
ID:	309791

      Item:
      Click image for larger version

Name:	item.jpg
Views:	1
Size:	26.7 KB
ID:	309792
      but the trigger didn't work,trigger:
      Click image for larger version

Name:	trigger.jpg
Views:	1
Size:	19.9 KB
ID:	309793

      Somebody know what I've done wrong?

      Comment

      • fossiel
        Junior Member
        • Jan 2012
        • 14

        #18
        Monitoring remote Windows service

        The solution is that I had the trigger like:
        {tstsvr:service_state[Spooler].max(0)}>0
        and this is the way it works:
        {tstsvr:service_state[Spooler].last(0)}>0

        so David thanks for the help.

        Comment

        Working...