舉報 
會員
The DevOps 2.2 Toolkit
ThisbookisforprofessionalsexperiencedwithDockerlookingtocreatebothself-adaptingandself-healingsystemsusingthesoftware.
最新章節
- Leave a review - let other readers know what you think
- Other Books You May Enjoy
- What now?
- Logic matters tools might vary
- Self-adaptation flow
- Request flow
品牌：中圖公司
上架時間：2021-06-24 17:56:24
出版社：Packt Publishing
本書數字版權由中圖公司提供，并由其授權上海閱文信息技術有限公司制作發行
- Leave a review - let other readers know what you think 更新時間：2021-06-24 18:46:45
- Other Books You May Enjoy
- What now?
- Logic matters tools might vary
- Self-adaptation flow
- Request flow
- Self-healing flow
- Infrastructure tasks
- Self-adaptation flow
- Request flow
- Reconfiguration flow
- Deployment flow
- Self-healing flow
- Service tasks
- Blueprint of a Self-Sufficient System
- What now?
- Scaling nodes when replica state is pending
- Rescheduling services after scaling nodes
- Scaling cluster nodes automatically
- Creating scaling job
- Scaling nodes manually
- Creating a cluster
- Self-Adaptation Applied to Infrastructure
- What now?
- Exploring fault tolerance
- Automating cluster setup
- Self-Healing Applied to Infrastructure
- What now?
- Extending the capacity of the cluster
- Setting up centralized logging
- Alternatives to CloudStor volume driver
- Persisting state
- Securing services
- Deploying services
- Creating a Docker for AWS cluster
- Setting Up a Production Cluster
- What now?
- Sending error notifications to slack
- Scaling services automatically
- Firing alerts based on instrumented metrics
- Querying metrics from instrumented services
- Scraping metrics from instrumented services
- Creating the cluster and deploying services
- Setting up the objectives
- Self-Adaptation Applied to Instrumented Services
- What now?
- Instrumenting services using histograms and summaries
- Instrumenting services using gauges
- Instrumenting services using counter
- Creating the cluster and deploying services
- Choosing instrumentation type
- Differentiating services based on their types
- Defining requirements behind service specific metrics
- Instrumenting Services
- What now?
- Cluster role in the system
- Scheduler role in the system
- Alerting role in the system
- Metrics role in the system
- Proxy role in the system
- Service configuration role in the system
- Continuous deployment role in the system
- Developer's role in the system
- Painting the Big Picture – The Self-Sufficient System Thus Far
- What now
- Integrating Alertmanager with Jenkins
- Notifying humans that scaling failed
- Preventing the scaling disaster
- Creating a scaling pipeline
- Preparing the system for alerts
- Creating the cluster and deploying services
- Choosing the tool for scaling
- Self-Adaptation Applied to Services
- What now?
- Is it enough to have self-healing applied to services?
- Using Docker Swarm for self-healing services
- Creating the cluster and deploying services
- Self-Healing Applied to Services
- The four quadrants of a dynamic and self-sufficient system
- Alerting the System
- What now?
- Using templates in Alertmanager configuration
- Setting up Alertmanager
- Creating the cluster and deploying services
- Alerting Humans
- What now?
- Using shortcuts to define alerts
- Defining additional alert information through labels and annotations
- Postponing alerts firing
- Defining multiple alerts for a service
- Creating alerts based on metrics
- Creating the cluster and deploying services
- Defining Cluster-Wide Alerts
- What now?
- Using memory reservations and limits in Prometheus
- Updating service constraints
- Querying metrics
- Exploring exporter metrics
- Deploying exporters
- Creating the cluster and deploying services
- Scraping Metrics
- What now?
- Integrating Docker Flow Monitor with Docker Flow Proxy
- Deploying Docker Flow Monitor
- Designing a more dynamic monitoring solution
- Deploying Prometheus stack
- Deploying and Configuring Prometheus
- What now?
- Which tool should we choose?
- Prometheus
- Nagios and Sensu
- InfluxDB
- Graphite
- Non-dimensional versus dimensional metrics
- Choosing a Solution for Metrics Storage and Query
- What now?
- What is a self-healing system?
- What is a self-adaptive system?
- Introduction to Self-Adapting and Self-Healing Systems
- Get in touch
- Conventions used
- Download the color images
- Download the example code files
- Overview
- Preface
- PacktPub.com
- Why subscribe?
- Packt Upsell
- Packt is searching for authors like you
- About the author
- Contributor
- Dedication
- Title Page
- coverpage
- coverpage
- Title Page
- Dedication
- Contributor
- About the author
- Packt is searching for authors like you
- Packt Upsell
- Why subscribe?
- PacktPub.com
- Preface
- Overview
- Download the example code files
- Download the color images
- Conventions used
- Get in touch
- Introduction to Self-Adapting and Self-Healing Systems
- What is a self-adaptive system?
- What is a self-healing system?
- What now?
- Choosing a Solution for Metrics Storage and Query
- Non-dimensional versus dimensional metrics
- Graphite
- InfluxDB
- Nagios and Sensu
- Prometheus
- Which tool should we choose?
- What now?
- Deploying and Configuring Prometheus
- Deploying Prometheus stack
- Designing a more dynamic monitoring solution
- Deploying Docker Flow Monitor
- Integrating Docker Flow Monitor with Docker Flow Proxy
- What now?
- Scraping Metrics
- Creating the cluster and deploying services
- Deploying exporters
- Exploring exporter metrics
- Querying metrics
- Updating service constraints
- Using memory reservations and limits in Prometheus
- What now?
- Defining Cluster-Wide Alerts
- Creating the cluster and deploying services
- Creating alerts based on metrics
- Defining multiple alerts for a service
- Postponing alerts firing
- Defining additional alert information through labels and annotations
- Using shortcuts to define alerts
- What now?
- Alerting Humans
- Creating the cluster and deploying services
- Setting up Alertmanager
- Using templates in Alertmanager configuration
- What now?
- Alerting the System
- The four quadrants of a dynamic and self-sufficient system
- Self-Healing Applied to Services
- Creating the cluster and deploying services
- Using Docker Swarm for self-healing services
- Is it enough to have self-healing applied to services?
- What now?
- Self-Adaptation Applied to Services
- Choosing the tool for scaling
- Creating the cluster and deploying services
- Preparing the system for alerts
- Creating a scaling pipeline
- Preventing the scaling disaster
- Notifying humans that scaling failed
- Integrating Alertmanager with Jenkins
- What now
- Painting the Big Picture – The Self-Sufficient System Thus Far
- Developer's role in the system
- Continuous deployment role in the system
- Service configuration role in the system
- Proxy role in the system
- Metrics role in the system
- Alerting role in the system
- Scheduler role in the system
- Cluster role in the system
- What now?
- Instrumenting Services
- Defining requirements behind service specific metrics
- Differentiating services based on their types
- Choosing instrumentation type
- Creating the cluster and deploying services
- Instrumenting services using counter
- Instrumenting services using gauges
- Instrumenting services using histograms and summaries
- What now?
- Self-Adaptation Applied to Instrumented Services
- Setting up the objectives
- Creating the cluster and deploying services
- Scraping metrics from instrumented services
- Querying metrics from instrumented services
- Firing alerts based on instrumented metrics
- Scaling services automatically
- Sending error notifications to slack
- What now?
- Setting Up a Production Cluster
- Creating a Docker for AWS cluster
- Deploying services
- Securing services
- Persisting state
- Alternatives to CloudStor volume driver
- Setting up centralized logging
- Extending the capacity of the cluster
- What now?
- Self-Healing Applied to Infrastructure
- Automating cluster setup
- Exploring fault tolerance
- What now?
- Self-Adaptation Applied to Infrastructure
- Creating a cluster
- Scaling nodes manually
- Creating scaling job
- Scaling cluster nodes automatically
- Rescheduling services after scaling nodes
- Scaling nodes when replica state is pending
- What now?
- Blueprint of a Self-Sufficient System
- Service tasks
- Self-healing flow
- Deployment flow
- Reconfiguration flow
- Request flow
- Self-adaptation flow
- Infrastructure tasks
- Self-healing flow
- Request flow
- Self-adaptation flow
- Logic matters tools might vary
- What now?
- Other Books You May Enjoy
- Leave a review - let other readers know what you think 更新時間：2021-06-24 18:46:45
