Details
-
Improvement
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
Operability
-
Low Hanging Fruit
-
All
-
None
-
Description
It is common that network scans happen for some companies, and when these scans happen they will send packets to the Cassandra ports which do not match our protocol; when this happens we fail and increment metrics to show this. To avoid these scans polluting our metrics, we should allow users to block their own IP subnets from updating these metrics.
Attachments
Issue Links
- causes
-
CASSANDRA-17026 UnableToParseClientMessageFromBlockedSubnetTest.badMessageCausesProtocolExceptionFromExcludeList failing on extra log entries
- Resolved
-
CASSANDRA-18002 Update NetBeans project file for dependency changes since 7th July 2021
- Resolved
- links to