You're reading from Multi-Cloud Architecture and Governance Leverage Azure, AWS, GCP, and VMware vSphere to build effective multi-cloud solutions

Product type Paperback

Published in Dec 2020

Publisher Packt

ISBN-13 9781800203198

Length 412 pages

Edition 1st Edition

Tools

AWS

Concepts

Cloud Computing

Authors (2):

Jeroen Mulder

View More author details

Table of Contents (28) Chapters

Preface

1. Section 1 – Introduction to Architecture and Governance for Multi-Cloud Environments

2. Chapter 1: Introduction to Multi-Cloud FREE CHAPTER

3. Chapter 2: Business Acceleration Using a Multi-Cloud Strategy

4. Chapter 3: Getting Connected – Designing Connectivity

5. Chapter 4: Service Designs for Multi-Cloud

6. Chapter 5: Managing the Enterprise Cloud Architecture

7. Section 2 – Getting the Basics Right with BaseOps

8. Chapter 6: Designing, Implementing, and Managing the Landing Zone

9. Chapter 7: Designing Resilience and Performance

10. Chapter 8: Defining Automation Tools and Processes

11. Chapter 9: Defining and Using Monitoring and Management Tools

12. Section 3 – Cost Control in Multi-Cloud with FinOps

13. Chapter 10: Managing Licenses

14. Chapter 11: Defining Principles for Resource Provisioning and Consumption

15. Chapter 12: Defining Naming Conventions and Tagging

16. Chapter 13: Validating and Managing Bills

17. Section 4 – Security Control in Multi-Cloud with SecOps

18. Chapter 14: Defining Security Policies

19. Chapter 15: Implementing Identity and Access Management

20. Chapter 16: Defining Security Policies for Data

21. Chapter 17: Implementing and Integrating Security Monitoring

22. Section 5 – Structured Development on Multi-Cloud Environments with DevOps

23. Chapter 18: Designing and Implementing CI/CD Pipelines

24. Chapter 19: Introducing AIOps in Multi-Cloud

25. Chapter 20: Introducing Site Reliability Engineering in Multi-Cloud

26. Assessments

27. Other Books You May Enjoy

Leave a review - let other readers know what you think

Consolidating and interpreting data from monitoring systems

The only thing a business needs to be interested in here is how events in IT impact the business' operations. To be able to discern this, we need to consolidate and interpret monitoring data.

The big question is this: when is data from monitoring relevant to the business? It doesn't make sense to inform a business leader about the performance of CPUs in virtual machines, but it does make sense to inform him or her when system capacity is lacking and hindering the speed of processing transactions. In that case, the business might lose money since transactions might be processed too slowly or, worse, dropped because of timeout failures.

When is data relevant to a business? In short, data should enable business decisions. Deploying extra virtual machines or scaling out environments are not business decisions. These are technical decisions. A business decision would be to launch a new product at a given moment...