elastic / elastic/logstash

[logstash][x-pack] configuration inconsistency with elastic & kibana

Open
#8,493 0 comments 6 reactions 0 assignees View on GitHub
enhancement v6.0.0-rc1
Dominant language
Java
Stars
14.9k
Forks
3.5k
Avg merge
1d 4h
Merged PRs (30d)
88

Description

In Elastic and Kibana, when x-pack is installed but the security is disabled, you have the following setting in config file:
```
xpack.security.enabled: false
```

But in logstash, this setting does not exist.
Instead, you have to provide and empty login and an empty password :
```
xpack.monitoring.elasticsearch.url: http://localhost:9201
xpack.monitoring.elasticsearch.username:
xpack.monitoring.elasticsearch.password:
```

Why not unify settings ?

Version : 6.0.0rc1

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the Logstash monitoring configuration documented in the issue, especially xpack.monitoring.elasticsearch.url, username, and password, and compare it with the xpack.security.enabled behavior described for Elastic and Kibana. Determine whether a unified disabled-security setting is feasible and document the expected configuration and validation for version 6.0.0rc1.

Written by the indexing model from the issue text.

Assessment

Tech stack
elasticsearch
Domain
observability-sre
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.