-
Notifications
You must be signed in to change notification settings - Fork 791
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
Fail to retrieve data from ELK 8.1.1,Is it possible that this version does not support Elasticsearch versions 8.X? #895
Comments
did you got it working for Elastic 8.X? I am also facing same issues. |
No, I haven't resolved it yet either. I'm also seeking guidance to solve this issue. |
I am not aware of any incompatibilities with 8.x as of this time. If you're having issues with the terminal and special characters in a password, single quote the entire es.uri value. |
For example, if the password is '#H755d8@chi7gf', it would be written like this: |
It would be the first one. The go library should handle the encoding automatically. |
--es.uri '[http://user:#H755d8@[email protected]:9200]' |
I was incorrect. If the password has special characters, they must be URL escaped before putting them into the es.uri argument. |
Eg:dial tcp: lookup user on [::1]:53: read udp [::1]:11958->[::1]:53: read: connection refused"
config:
ExecStart=/data/es_exporter/elasticsearch_exporter-1.7.0/elasticsearch_exporter
--es.all
--es.indices
--es.shards
--es.aliases
--es.indices_settings
--collector.clustersettings
--es.indices_mappings
--es.data_stream
--es.timeout=10s
--web.listen-address=x.x.x.x:9114
--es.uri http://user:[email protected]:9200
Q2:How should the password be written if it contains the "#" or "@" character?
Thanks!
The text was updated successfully, but these errors were encountered: