Config for Monitoring Windows Services by heartbeat error

[Mehak_Bhargava]

I have my elasticsearch, logstash, kibana running inside docker. The files filebeat ships are from another server. Firstly, I just want to see if up/down status is provided for windows services.

• Can I install heartbeat on the filebeat server where my logs are or is it better to install on docker?
• If I install heartbeat inside docker ,this will be my configuration file for heartbeat-

heartbeat.monitors:
- type: icmp
  hosts: ["xxxxx"]
  schedule: '@every 10s'
  timeout: 16s
- type: icmp
  hosts: ["xxxx"]

I am not sure how to define monitoring windows service's for url.

[Mehak_Bhargava]

@Andrew_Cholakian1 I read your comment on a post similar to this. Could you please help?

Heartbeat Monitoring for Windows Servers

I have tried to setup heartbeat monitoring for windows servers. I have setup IMCP through the Module.d folder. The heartbeat service starts and shows the server as up. I can power down the server and the monitor still shows as up. How can I fix this and what did I not setup correctly? Thanks in Advance

[Andrew_Cholakian1 (Andrew Cholakian)]

We only support monitoring of icmp/tcp/http with heartbeat. If your service responds to these protocols you can monitor that.

Generally, people install a central heartbeat or two to monitor many boxes, but you don't have to do things this way.