-
Notifications
You must be signed in to change notification settings - Fork 51
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
.ops: add ecamp3-logging #5039
.ops: add ecamp3-logging #5039
Conversation
2578513
to
c34e799
Compare
Yes, but with the fluent operator and fluentbit and fluentd instead of filebeat.
Currently on dev it looks like this:
So we would need another node. Maybe 2 if elasticsearch contains a lot of logs, we will see.
Yes, you can do a port forward with |
That we don't need kubectl to access these internal services. Can be used for the kibana from ecamp#5039, or the kubernetes dashboard from ecamp#4134
.ops/ecamp3-logging/templates/fluentd/fluentd_clusterfilter.yaml
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.
Looks great, thanks a lot!
.ops/ecamp3-logging/templates/elasticsearch/elasticsearch_stateful_set.yaml
Outdated
Show resolved
Hide resolved
This adds the EFFK (Elasticsearch, fluentbit, fluentd, Kibana) stack to the ops folder. Kibana and Elasticsearch taken from https://www.digitalocean.com/community/tutorials/how-to-set-up-an-elasticsearch-fluentd-and-kibana-efk-logging-stack-on-kubernetes
c34e799
to
b3827a3
Compare
Finally i have a branch again which works.
Now with a lot less yaml.
This adds the EFFK (Elasticsearch, fluentbit, fluentd, Kibana) stack to the ops folder.
Kibana and Elasticsearch taken from
https://www.digitalocean.com/community/tutorials/how-to-set-up-an-elasticsearch-fluentd-and-kibana-efk-logging-stack-on-kubernetes
For the full story, see: #4775