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

Fail to retrieve data from ELK 8.1.1,Is it possible that this version does not support Elasticsearch versions 8.X? #895

Open
TYQ33 opened this issue May 17, 2024 · 7 comments

Comments

@TYQ33
Copy link

TYQ33 commented May 17, 2024

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!

@archana-punia
Copy link

did you got it working for Elastic 8.X? I am also facing same issues.

@TYQ33
Copy link
Author

TYQ33 commented May 22, 2024

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.

@sysadmind
Copy link
Contributor

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.

@TYQ33
Copy link
Author

TYQ33 commented May 24, 2024

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:
--es.uri 'http://user:#H755d8@[email protected]:9200' Or --es.uri 'http://user:%23H755d8%[email protected]:9200'
Which one is correct? Thanks!

@sysadmind
Copy link
Contributor

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:
--es.uri 'http://user:#H755d8@[email protected]:9200' Or --es.uri 'http://user:%23H755d8%[email protected]:9200'
Which one is correct? Thanks!

It would be the first one. The go library should handle the encoding automatically.

@TYQ33 TYQ33 closed this as completed Aug 6, 2024
@TYQ33 TYQ33 reopened this Aug 6, 2024
@TYQ33
Copy link
Author

TYQ33 commented Aug 6, 2024

--es.uri '[http://user:#H755d8@[email protected]:9200]'
This is incorrect."How should it be written correctly?"

@sysadmind
Copy link
Contributor

I was incorrect. If the password has special characters, they must be URL escaped before putting them into the es.uri argument.

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

No branches or pull requests

3 participants