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
Add an example of autodiscover to deployment manifests #8029
Conversation
Autodiscover is not enabled by default (yet) in our example manifests. This change includes examples on how to enable it for Filebeat and Metricbeat. This should ease the task for users who are willing to use autodiscover.
f33982b
to
00c9276
Compare
#metricbeat.autodiscover: | ||
# providers: | ||
# - type: kubernetes | ||
# host: ${HOSTNAME} |
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.
Is $HOSTNAME
always set? and is it always set to a hostname in the list of nodes? (e.g. I think nodes can be registered with their IPs)
Alternatively we can add the NODE_NAME
environment variable.
- name: NODE_NAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
done! |
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, thanks for adding this 🙂
Autodiscover is not enabled by default (yet) in our example manifests. This change includes examples on how to enable it for Filebeat and Metricbeat. This should ease the task for users who are willing to use autodiscover. (cherry picked from commit 37b1e63)
Autodiscover is not enabled by default (yet) in our example manifests. This change includes examples on how to enable it for Filebeat and Metricbeat. This should ease the task for users who are willing to use autodiscover. (cherry picked from commit 37b1e63)
Autodiscover is not enabled by default (yet) in our example manifests. This change includes examples on how to enable it for Filebeat and Metricbeat. This should ease the task for users who are willing to use autodiscover. (cherry picked from commit 37b1e63)
Autodiscover is not enabled by default (yet) in our example manifests. This change includes examples on how to enable it for Filebeat and Metricbeat. This should ease the task for users who are willing to use autodiscover. (cherry picked from commit 37b1e63)
…elastic#8037) Autodiscover is not enabled by default (yet) in our example manifests. This change includes examples on how to enable it for Filebeat and Metricbeat. This should ease the task for users who are willing to use autodiscover. (cherry picked from commit 71c3ffd)
Autodiscover is not enabled by default (yet) in our example manifests.
This change includes examples on how to enable it for Filebeat and
Metricbeat.
This should ease the task for users who are willing to use autodiscover.
I also updated default settings to adapt manifests to latest changes in 6.4 (automatic enriching of events from Kubernetes module)