-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
packetbeat 5.x memcache cannot be disabled #4335
Comments
Could you please share your exact packetbeat version and your full packetbeat config file? |
I tested packetbeat 5.4.0 and 5.2.1 with following command
|
To disable memcache, you have to comment out the complete block:
Can you please try that? |
I can do that, while disabling other protocols doesn't need to do so, i can just comment out the list of ports as the instruction says. |
Commenting out the line with packetbeat.protocols.memcache: changes the BPF filter to ''. |
The documentation states that the memcache proto can be disabled by commenting out the list of ports. In practice one had to comment out the entire line. Fix it by not initializing the Ports variable inside the defaultConfig of the memcache proto. No other proto has Ports initialized in the defaultConfig.
The documentation states that the memcache proto can be disabled by commenting out the list of ports. In practice one had to comment out the entire line. Fix it by not initializing the Ports variable inside the defaultConfig of the memcache proto. No other proto has Ports initialized in the defaultConfig.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
For confirmed bugs, please report:
packetbeat 5.x
macosx, suselinux
1)annotate memcache's port 11211 in packetbeat.yml
2)run packetbeat with -d "sniffer" option
3)you can see the 11211 is still on
The text was updated successfully, but these errors were encountered: