Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

false warning for elasticsearch output config when using monitoring #10352

Closed
jpcarey opened this issue Jan 25, 2019 · 16 comments · Fixed by #12749
Closed

false warning for elasticsearch output config when using monitoring #10352

jpcarey opened this issue Jan 25, 2019 · 16 comments · Fixed by #12749

Comments

@jpcarey
Copy link

jpcarey commented Jan 25, 2019

In 6.5.4, if you have monitoring setup - it produces a false warning for logstash.outputs.elasticsearch. I'm not sure why this message is triggered at all, and why it is flagged as logstash.outputs.elasticsearch instead of the appropriate monitoring module.

[2019-01-11T11:16:28,685][WARN ][logstash.outputs.elasticsearch] ** WARNING ** Detected UNSAFE options in elasticsearch output configuration!
** WARNING ** You have enabled encryption but DISABLED certificate verification.
** WARNING ** To make sure your data is secure change :ssl_certificate_verification to true 
[2019-01-11T11:16:28,654][WARN ][logstash.outputs.elasticsearch] You are using a deprecated config setting "document_type" set in elasticsearch.
@Pectojin
Copy link

Facing the same issue in 6.6.2. There's no monitoring value for setting validation either which makes you wonder if it's a false warning or a default false value that can't be changed.

@jgrevich
Copy link

jgrevich commented Mar 16, 2019

I noticed the same issue with a cluster running 6.4.2. I also verified with tcpdump+wireshark that it's a false alarm and all elasticsearch outputs are using tls1.2 as configured.

@davtex
Copy link

davtex commented May 15, 2019

Facing same problem in 7.0.1. I assume there are incorrect defaults configured for monitoring exporter.

@elastic elastic deleted a comment from MorrieAtElastic Jul 11, 2019
@fholzer
Copy link

fholzer commented Jul 22, 2019

I though it may have been fixed in 78bc47d
but after installing 7.2 and setting xpack.monitoring.elasticsearch.ssl.verification_mode: certificate the warning still shows up.

@saifat29
Copy link

saifat29 commented Aug 19, 2019

Having same issue on 7.2.0

@rustamxp
Copy link

Have the same issue on 7.3.0

@geekpete
Copy link
Member

Seems a few related or possibly duplicate issues around this:
#10524
#9716
#9734

possibly related upstream issue:
cheald/manticore#52

@Erni
Copy link

Erni commented Aug 30, 2019

Facing the same issue in 6.8

@adoerrES
Copy link

Another user also experiencing the issue in 6.8.

@mohclips
Copy link

Same on 7.4

@danlsgiga
Copy link

danlsgiga commented Jan 9, 2020

Same on 7.5.1

@maggieghamry
Copy link

Same issue on 7.6

@rom1b31
Copy link

rom1b31 commented May 27, 2020

Same issue on 7.6.1

@rhizoet
Copy link

rhizoet commented Jun 22, 2020

Always same on latest 7.8.0. Please fix. This makes me and my teammates nervous 😆

@aruandre
Copy link

aruandre commented Nov 5, 2020

same on 7.9.3

@sastorsl
Copy link

sastorsl commented Feb 18, 2021

And on 7.11.1

The documentation explicitly says that certificate validation is enabled by default:
https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html#plugins-outputs-elasticsearch-ssl_certificate_verification

Even explicitly setting it still produces the warning.

output {
    elasticsearch {
    ...
    ssl => true
    ssl_certificate_verification => true
    ....
    }
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.