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
Description of the problem including expected versus actual behavior
Logstash has node and pipeline level metric collection control signal. As of now (after #16864 fix), users will be able to disable pipeline level metric collection. However, when node level metric collection disable is impossible which leads endpoint failure. Extra notes: not to confuse with api.enabled which disables the LS web server, it has broader context than metrics that loggin CRUD operations can be proceed.
Acceptance Criteria
Fix the current bug;
End users should have a meaningful guidance (reasoning and guide to enable back) when metric collection disabled and hit the endpoints
Documentation to highlight metric collection enable/disable
Steps to reproduce:
Use Logstash built from main or 8.17.0
Set metric.collect: false in logstash.yml
Run Logstash
Hit the localhost:9600/_node/stats endpoint
which results error in both LS console/log and endpoint result.
Description of the problem including expected versus actual behavior
Logstash has node and pipeline level metric collection control signal. As of now (after #16864 fix), users will be able to disable pipeline level metric collection. However, when node level metric collection disable is impossible which leads endpoint failure.
Extra notes: not to confuse with
api.enabled
which disables the LS web server, it has broader context than metrics that loggin CRUD operations can be proceed.Acceptance Criteria
Steps to reproduce:
main
or 8.17.0metric.collect: false
inlogstash.yml
localhost:9600/_node/stats
endpointwhich results error in both LS console/log and endpoint result.
Provide logs
The text was updated successfully, but these errors were encountered: