Details
-
Bug
-
Resolution: Fixed
-
Low
-
8.20.1, 8.20.3, 8.20.6
-
None
-
8.2
-
1
-
Severity 3 - Minor
-
Description
Issue Summary
According to Jira Cluster Monitoring, there are several events which should get captured in the Audit log:
We log the following events:
- NodeJoined - a new node has joined the cluster
- NodeReJoined - an existing node was restarted and re-joined the cluster
- NodeLeft - a node received the OFFLINE status
- NodeRemoved - a node was removed from the cluster
- NodeUpdated - all other cases when existing node was updated
This is reproducible on Data Center: Yes
Steps to Reproduce
- Configure a two node DC cluster
- Turn up 'Global configuration and administration' coverage to 'Full'
- Restart one of the nodes
- Filter Audit log results by 'clustering' category
- Note that only "Node deactivated" event is logged, and when the node restarts, no 'NodeReJoined' event is captured.
Expected Results
It is expected that a NodeReJoined event will get logged after the restart.
Actual Results
Only NodeRemoved events get logged.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available