You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I guess I will not be that much effort as you already wrote the metricbeat cookbook which has windows support and the beats installation is similar to packetbeat.
The text was updated successfully, but these errors were encountered:
Oh, I found out that there actually are quite a few differences
Windows version needs winpcap
There is a wireshark cookbook, maybe that one helps.
Configuration does not allow to capture all interfaces at one.
I guess that we need to make it in such a way that we can provide multiple configuration files and chef-client creates one packetbeat installation for each so we can capture multiple devices.
Another way of solving the 2nd problem might be to have an attribute which is an array where we can insert the device IDs, provide one common config file without device id and chef-client will copy that file into a new packetbeat instance for all the device IDs specified, adding the device ID accordingly to every config file.
The device ID doesn't have to be specified in the packetbeat.yml config file.
It can be provided via the command line. So an array in the chef attributes could be used to insert the required Device IDs there.
Then, packetbeat can be started as follows multiple times
.\packetbeat.exe -c .\packetbeat.yml -E packetbeat.interfaces.device=<ID_FROM_CHEF_ATTRIBUTE>
Thanks for this great cookbook!
Please add support for Windows Nodes.
I guess I will not be that much effort as you already wrote the metricbeat cookbook which has windows support and the beats installation is similar to packetbeat.
The text was updated successfully, but these errors were encountered: