Skip to content

Connect to Elasticsearch API via IP address #156

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

Merged
merged 1 commit into from
May 15, 2023
Merged

Connect to Elasticsearch API via IP address #156

merged 1 commit into from
May 15, 2023

Conversation

widhalmt
Copy link
Member

For environments where we can't use DNS resolution, we should connect to Elasticsearch API via IP address instead of hostname.

fixes #155

@widhalmt widhalmt added the bug Something isn't working label May 12, 2023
@widhalmt widhalmt added this to the 1.0.0 milestone May 12, 2023
@widhalmt widhalmt self-assigned this May 12, 2023
@widhalmt widhalmt enabled auto-merge May 12, 2023 13:29
Copy link
Member

@lcndsmr lcndsmr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works

@widhalmt widhalmt added this pull request to the merge queue May 15, 2023
Merged via the queue into main with commit 33a4943 May 15, 2023
@widhalmt widhalmt deleted the fix/nodns-155 branch May 15, 2023 10:29
ivareri pushed a commit to ivareri/ansible-collection-elasticstack that referenced this pull request Jun 17, 2025
For environments where we can't use DNS resolution, we should connect to
Elasticsearch API via IP address instead of hostname.

fixes NETWAYS#155
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Creating Logstash users uses hostname and fails if no DNS is available
2 participants