Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
The Road to Azure Cost Governance

You're reading from  The Road to Azure Cost Governance

Product type Book
Published in Feb 2022
Publisher Packt
ISBN-13 9781803246444
Pages 314 pages
Edition 1st Edition
Languages
Authors (2):
Paola E. Annis Paola E. Annis
Profile icon Paola E. Annis
Giuliano Caglio Giuliano Caglio
Profile icon Giuliano Caglio
View More author details
Toc

Table of Contents (14) Chapters close

Preface 1. Section 1: Cloud Cost Management
2. Chapter 1: Understanding Cloud Bills 3. Chapter 2: What Does Your Cloud Spending Look Like? 4. Chapter 3: Monitoring Costs 5. Section 2: Cloud Cost Savings
6. Chapter 4: Planning for Cost Savings – Right-Sizing 7. Chapter 5: Planning for Cost Savings – Cleanup 8. Chapter 6: Planning for Cost Savings – Reservations 9. Section 3: Cost- and Carbon-Aware Cloud Architectures
10. Chapter 7: Application Performance and Cloud Cost 11. Chapter 8: Sustainable Applications and Architectural Patterns 12. Assessments 13. Other Books You May Enjoy

Identifying cost spikes

As we learned in Chapter 1, Understanding Cloud Bills, and Chapter 3, Monitoring Costs, at this stage, you should be familiar with all the tools that allow you to get a full picture of your spending and keep it predictable and under budget. Sometimes, however, there are specific conditions that will create unexpected spikes in your costs and will call for a prompt cleanup action. My recommendation is to check the Azure Cost Management page daily and look at a daily stacked view of your spending. The following screenshot shows the cost management page:

Figure 5.7 – Example of a daily stacked chart on your cost management page

In normal operations, you should be able to identify a nice clean pattern (just as the one pictured in the previous example) and immediately spot any spikes that do not resemble your normal pattern of operations.

Spikes can be caused by many underlying issues:

  • An application that is calling a service...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}