Containers-roadmap: Add Monitoring Section to EKS User Guide

[mrichman]

The EKS User Guide has no information on monitoring the cluster using CloudWatch or other tooling.

This documentation could detail the installation and configuration of Fluentd for log aggregation into Cloudwatch Logs, as well as Prometheus and Grafana installation.

I realize the latter two are not AWS-specific, but are probably common enough use cases to include in the product documentation.

[pawelprazak]

Maybe consider filebeat, logstash (on EKS) and the hosted ElasticSearch with Kibana for logging instead of Fluentd and Cloudwatch.

[ffjia]

@pawelprazak why use filebeat instead of fluentd?

[pawelprazak]

I have bad experience with running fluentd

wt., 23 lip 2019, 04:36 użytkownik Feifei Jia [e-mail]
napisał:

@pawelprazak https://github.com/pawelprazak why use filebeat instead of
fluentd?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws/containers-roadmap/issues/61?email_source=notifications&email_token=AAAL52VH3P7XH5Y74AE3VZTQAZVBVA5CNFSM4GKJ66X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2RXP4Y#issuecomment-514029555,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAL52RCNPCVYGP7I4DVC43QAZVBVANCNFSM4GKJ66XQ
.

[whereisaaron]

@mrichman there are fairly good instructions for on the eksworkshop website for deploying Fluentd with Cloudwatch, Elasticsearch, and Kibana.
https://eksworkshop.com/logging/

Many log tools are possible, but we always use fluentd with Kubernetes for its excellent, structured Kubernetes metadata. It has always been reliable for us.

[Bessonov]

May be relevant: https://docs.aws.amazon.com/eks/latest/userguide/logging-monitoring.html (and links inside)