Book Image

Mastering Docker Enterprise

By : Mark Panthofer
Book Image

Mastering Docker Enterprise

By: Mark Panthofer

Overview of this book

While known mostly as the open source engine behind tens of millions of server nodes, Docker also offers commercially supported enterprise tooling known as the Docker Enterprise. This platform leverages the deep roots from Docker Engine - Community (formerly Docker CE) and Kubernetes, but adds support and tooling to efficiently operate a secure container platform at scale. With hundreds of enterprises on board, best practices and adoption patterns are emerging rapidly. These learning points can be used to inform adopters and help manage the enterprise transformation associated with enterprise container adoption. This book starts by explaining the case for Docker Enterprise, as well as its structure and reference architecture. From there, we progress through the PoC,pilot and production stages as a working model for adoption, evolving the platform’s design and configuration for each stage and using detailed application examples along the way to clarify and demonstrate important concepts.The book concludes with Docker’s impact on other emerging software technologies, such as Blockchain and Serverless computing. By the end of this book, you’ll have a better understanding of what it takes to get your enterprise up and running with Docker Enterprise and beyond.
Table of Contents (17 chapters)
Free Chapter
1
Section 1: Getting Started with Docker Enterprise
5
Section 2: Piloting Docker Enterprise
10
Section 3: In Production with Docker Enterprise

Pilot Docker Enterprise Platform Monitoring and Logging

As we wind down our pilot phase, we need to think about how we are going to support our pilot application during the internal pilot. Beyond the external access metrics like https://www.site24x7.com/ and others do so well, we need to get start getting real experience in container logging and monitoring.

Logging and monitoring is a transformational area where we have to be careful not to pave the cowpath. In other words, it would be easy to carry some old habits into the new world of containers, but it could be problematic. Traditionally, we set up our application servers to handle logging. We usually did this in one of two ways. We either used logging frameworks to write logs to the application server's filesystem, or we installed agents on each of these servers to monitor the logging activity. Because we had a relatively...