-
Notifications
You must be signed in to change notification settings - Fork 707
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
Document Logstash connection to external Elasticsearch #6895
Conversation
if the URL is HTTPS and does not specify the port
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - I have a documentation suggestion, and a nit on test naming
metadata: | ||
name: external-es-ref | ||
stringData: | ||
url: https://abcd-42.xyz.elastic-cloud.com <1> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should add a note somewhere that we add the default port of 443
to https
URLs, as this is different behavior to standard logstash plugins, and different to how non-cloud Elasticsearch works out of the box
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I am slightly -1 on the port appending. As explained in my comment it does fix the problem only for Logstash and not for any of the other stack applications e.g. the Beats used for monitoring. I think I would favour calling out explicitly in the doc that the default port expected is 9200 and any other port has to be configured explicitly via the url.
monitoring: | ||
metrics: | ||
elasticsearchRefs: | ||
- secretName: external-es-ref <5> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assuming a user specifies a URL without explicit port in the secret, then the changes in this PR append 443 by default for the environment. However Beats also assume 9200 by default and while the Logstash side is fixed, the monitoring will still not work until the user fixes the url
field in the secret to include a port.
Co-authored-by: Rob Bavey <rob.bavey@elastic.co>
Kibana assumes 443. Beats and Logstah assume 9200. Not sure what the default port is for others. The stack monitoring is not consistent. |
docs/orchestrating-elastic-stack-applications/logstash.asciidoc
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: Peter Brachwitz <peter.brachwitz@gmail.com>
@kaisecheng should I merge this? |
@pebrc Yes please! |
This PR adds doc for connecting external Elasticsearch.