Disable monitoring in ML multinode tests#55461
Disable monitoring in ML multinode tests#55461williamrandolph merged 1 commit intoelastic:masterfrom
Conversation
Removing the deprecated "xpack.monitoring.enabled" setting introduced log spam and potentially some failures in ML tests. It's possible to use a different, non-deprecated setting to disable monitoring, so we do that here.
|
Pinging @elastic/es-core-infra (:Core/Infra/Core) |
|
There is also a place in Java code where ML is disabling monitoring using the deprecated setting: Should that also be flipped over to using In fact, if you search for usages of |
|
@droberts195 I was thinking of doing those in a follow-up PR but I'll go ahead and handle them here. |
droberts195
left a comment
There was a problem hiding this comment.
I was thinking of doing those in a follow-up PR
@williamrandolph if you think there's a risk of breaking other things then a follow-up PR is fine with me.
LGTM for the changes so far.
Removing the deprecated "xpack.monitoring.enabled" setting introduced log spam and potentially some failures in ML tests. It's possible to use a different, non-deprecated setting to disable monitoring, so we do that here.
|
Backported to 7.x: 7817948 |
Removing the deprecated "xpack.monitoring.enabled" setting introduced log spam and potentially some failures in ML tests. It's possible to use a different, non-deprecated setting to disable monitoring, so we do that here.
Relates #55420
Relates #54816