Abstract
As you've seen throughout this book, embracing a microservices architecture will mean that your production environment has a large number of deployable units, which you will be ultimately responsible for making sure are functioning as expected, based on your requirements. As with any type of software, you will want to know when issues are happening, ideally before they start to affect your company's business metrics, such as user visits, signups, or sales. In some cases, it could take hours—or days—to find out that one small piece of software is malfunctioning, and you don't want to discover production issues after your users do.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsNotes
- 1.
“Make Data Useful,” Greg Linden, November 29, 2006; Presentation at Stanford University; https://docs.google.com/viewer?a=v&pid=sites&srcid=ZGVmYXVsdGRvbWFpbnxnbGluZGVufGd4OjVmZDIzMWMzMGI4MDc3OWM
- 2.
“Service-level agreement,” Wikipedia, referenced on August 27, 2016. https://en.wikipedia.org/wiki/Service-level_agreement
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2016 Cloves Carneiro Jr. and Tim Schmelmer
About this chapter
Cite this chapter
Carneiro, C., Schmelmer, T. (2016). Monitoring Your Services. In: Microservices From Day One. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-1937-9_13
Download citation
DOI: https://doi.org/10.1007/978-1-4842-1937-9_13
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-1936-2
Online ISBN: 978-1-4842-1937-9
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books