目錄(134章)
倒序
- 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
推薦閱讀
- 中國人才創新創業優質生態圈發展報告：對北上廣深杭5市25區的第三方評估（2018）
- 卓越工作：從優秀到卓越的高效工作法
- 悅讀MOOK（第十九卷）
- 我們時代的精神狀況
- 一帶一路：邁向治理現代化的大戰略
- 全球土地2016：熱點與前沿
- 科學技術與社會發展研究
- 助殘志愿服務實務指南
- 生態文明中的生態原理
- 做好會議記錄（第四版）
- 咨詢心理學
- 公共關系：理論與實務
- 寶貝取名有學問
- 百喻經故事全集
- 社會的惡與善
- 百弊放言
- “一帶一路”沿線國家五通指數報告（2017）
- 容忍比自由更重要
- 中國哲學社會科學發展歷程回憶·文學卷
- 黃侃：志氣為先（文化怪杰）
- 近代以來日本的中國觀（第一卷·總論）
- 和聲2010：在經濟與文化視野中審視文明
- 老夫子品評墨子
- 新時期婚姻倫理與生活質量研究：1980—2014
- 時政談屑
- 老夫子品評管子
- SPSS 19.0統計分析綜合案例詳解
- 李贄：告別中庸（文化怪杰）
- 中國人文社會科學國際論文統計分析：基于SSCI和A&HCI數據（2005-2009）
- 抗爭與合作：鄉村治理中的傳播模式
