Packetbeat MongoDB in Windows Server doesn't work

Elastic Stack Beats
1

Hi I'm trying to monitor mongodb connections using packetbeat, doing it locally on my mongodb works fine:
this is my configuration:

packetbeat.interfaces:
  - device: \Device\NPF_{422A5385-8A2F-46AB-8B71-2C94764B14FA}
  - device: \Device\NPF_Loopback
packetbeat.interfaces.poll_default_route: 1m
packetbeat.interfaces.internal_networks:
  - private
packetbeat.protocols:
- type: mongodb
  enable: true
  send_request: true
  send_response: true
  max_docs: 0
  max_doc_length: 0
  ports: [27017]

output.elasticsearch:
  hosts: ["localhost:9200"]
  protocol: "https"
  username: "elastic"
  password: "changeme"
  ssl.enabled: true
  ssl.verification_mode: none
  1. First I ran packetbeat devices to list all and then I had to add them manually because the default_device didn't work.
  2. Then I started and connected my local MongoDB to my local Compass and then I get the results
  3. If I try to do the same in an Azure Blade, I don't get any results both, in the Server and the Client. Any idea how to troubleshoot it? I do see the connections in the perfmon in Windows connecting via 27017, but not in metricbeat

Server (mongodb) is Windows Server 2019, and the client machines are in both in Windows 10 and Windows Server 2019

Cheers!

A

2

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.