-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Comments
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 |
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. |
Facing same problem in 7.0.1. I assume there are incorrect defaults configured for monitoring exporter. |
I though it may have been fixed in 78bc47d |
Having same issue on 7.2.0 |
Have the same issue on 7.3.0 |
Seems a few related or possibly duplicate issues around this: possibly related upstream issue: |
Facing the same issue in 6.8 |
Another user also experiencing the issue in 6.8. |
Same on 7.4 |
Same on 7.5.1 |
Same issue on 7.6 |
Same issue on 7.6.1 |
Always same on latest 7.8.0. Please fix. This makes me and my teammates nervous 😆 |
same on 7.9.3 |
And on 7.11.1 The documentation explicitly says that certificate validation is enabled by default: Even explicitly setting it still produces the warning.
|
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 aslogstash.outputs.elasticsearch
instead of the appropriate monitoring module.The text was updated successfully, but these errors were encountered: