Book Image

The DevOps 2.1 Toolkit: Docker Swarm

By : Viktor Farcic
Book Image

The DevOps 2.1 Toolkit: Docker Swarm

By: Viktor Farcic

Overview of this book

Viktor Farcic's latest book, The DevOps 2.1 Toolkit: Docker Swarm, takes you deeper into one of the major subjects of his international best seller, The DevOps 2.0 Toolkit, and shows you how to successfully integrate Docker Swarm into your DevOps toolset. Viktor shares with you his expert knowledge in all aspects of building, testing, deploying, and monitoring services inside Docker Swarm clusters. You'll go through all the tools required for running a cluster. You'll travel through the whole process with clusters running locally on a laptop. Once you're confident with that outcome, Viktor shows you how to translate your experience to different hosting providers like AWS, Azure, and DigitalOcean. Viktor has updated his DevOps 2.0 framework in this book to use the latest and greatest features and techniques introduced in Docker. We'll go through many practices and even more tools. While there will be a lot of theory, this is a hands-on book. You won't be able to complete it by reading it on the metro on your way to work. You'll have to read this book while in front of the computer and get your hands dirty.
Table of Contents (22 chapters)
Title Page
Credits
About the Author
www.PacktPub.com
Customer Feedback
Preface
11
Embracing Destruction: Pets versus Cattle

Exploring Docker Swarm and container overview dashboard in Grafana


One of the things missing from the dashboard are host names. If you select the Hostnames list, you'll notice that it is empty. The reason behind that lies in the node-exporter service. Since it is running inside containers, it is oblivious of the name of the underlying host.

We already commented that IPs from the node-exporter are not very valuable since they represent addresses of network endpoints. What we truly need are either "real" host IPs or host names. Since we cannot get the real IPs from Docker services, the alternative is to use host names instead. However, the official Node Exporter container does not provide that so we'll need to resort to an alternative. We'll change our node-exporter service with the image created by GitHub user bvis. The project can be found in the bvis/docker-node-exporter (https://github.com/bvis/docker-node-exporter) GitHub repository. Therefore, we'll remove the node-exporter service and...