Implementing Enterprise Observability for Success

Preface
Part 1 – Understanding Observability in the Real World
1
Why Observe?
What is observability?
What was used before observability?
Issues with traditional monitoring techniques
Modern infrastructure
Pre-empting issues
Identifying why and where the problem exists
Key benefits of observability
Summary
2
The Fundamentals of Observability
Understanding logs, metrics, and traces
Logs
Metrics
Traces
Getting to know service views
User experience maps
Customer journey maps (processes)
System maps
Service aggregate maps
Exploring CMDBs
What is a CMDB?
Why is a CMDB important?
CMDB providers and their life cycles
Identifying KPIs
Google’s golden signals
Summary
3
The Real World and Its Challenges
Is observability difficult to implement?
Google versus a financial institution
Diverse service versus focused service
Technology leader versus follower
Challenges faced by organizations in the real world
Infrastructure and architecture complexity
Mindset and culture
A lack of executive support
Tools galore
Mechanisms to measure success
The price tag
Overcoming challenges
Navigating through infrastructure and architectural complexity
Taking stock of your estate
How can executives help?
Tool rationalization and usage
What does success look like?
Cost rationalization
Summary
4
Collecting Data to Set Up Observability
Data collection layer one – Infrastructure
Understanding infrastructure
Collecting data to monitor infrastructure
Using infrastructure data
Data collection layer two – The application
Data collection for monitoring the application
Collecting application log data
APM data
Telemetry
Data collection layer three – the business service
Digital experience monitoring
Synthetic transaction monitoring
Endpoint monitoring
Real user monitoring
Data collection layer four – The organization
Summary
5
Observability Outcomes: Dashboards, Alerts, and Incidents
Getting to know dashboards
Introducing alerts and incidents
Alerts and incidents – the finer details
At what point should an alert be set up?
What should be the frequency of the alert?
How to manage alerts?
Observability consumers – self healing
Summary
Part 2 – Planning and Implementation
6
Gauging the Organization for Observability Implementation
Organization and culture
Assessing and driving the organization’s culture
Being data-driven
Ensuring data literacy
Providing executive endorsement
Establishing a governance model
Summary
7
Achieving and Measuring Observability Success
Exploring observability maturity levels
Initial
Managed
Defined
Quantitatively Managed
Optimized
Understanding people and skills
Technical skills
Communication skills
Problem-solving skills
Mapping skills and maturity levels
Measuring observability
Summary
8
Identifying the Stakeholders
Enhancement drivers of an organization
The actors of observability
How users prompt improvement
Exploring the supporters of observability
Enterprise architects
Enterprise data team
Sourcing team
Compliance and regulatory teams
Introducing the RASCI matrix
Summary
9
Deciding the Tools for Observability
Developing a strategy
Desirable features of observability tools
Build, leverage, or buy?
Exploring observability tools
Emerging observability trends
Standardizing observability for open source projects
Increased adoption of tracing
Enhancing security with observability
Auto-healing
Considering the total cost of ownership for observability
Summary
Part 3 – Use Cases
10
Kickstarting Your Own Observability Journey
Understanding the observability implementation workflow
Preparation – organization-wide change
Implementation – adoption by the organization
Case study 1 – goFast
Identifying the problem
Addressing the problem
Case study 2 – superEats
Identifying the problem
Addressing the problem
Case study 3 – bigBuys
Identifying the problem
Addressing the problem
Case study 4 – gruvyCars
Identifying the problem
Addressing the problem
Summary
Index
Other Books You May Enjoy