You know what to do. Destroy the cluster if you created it specifically for this chapter.
Before you leave, you might want to go over the main points of this chapter.
- For any but the smallest systems, going from one resource to another and from one node to another to find the cause of an issue is anything but practical, reliable, and fast.
- More often than not, kubectl logs command does not provide us with enough options to perform anything but simplest retrieval of logs.
- Elasticsearch is excellent, but it does too much. Its lack of focus makes it inferior to Prometheus for storing and querying metrics, as well as sending alerts based on such data.
- Logs themselves are too expensive to parse, and most of the time they do not provide enough data to act as metrics.
- We need logs centralized in a single location so that we can explore logs from any part of the system.
- We...