Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Microservices with Go

You're reading from   Microservices with Go The expert's guide to building secure, scalable, and reliable microservices with Go

Arrow left icon
Product type Paperback
Published in Jun 2025
Publisher Packt
ISBN-13 9781836207337
Length 428 pages
Edition 2nd Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Alexander Shuiskov Alexander Shuiskov
Author Profile Icon Alexander Shuiskov
Alexander Shuiskov
Arrow right icon
View More author details
Toc

Table of Contents (23) Chapters Close

Preface 1. Introduction FREE CHAPTER
2. Introduction to Microservices 3. Foundation
4. Scaffolding a Go Microservice 5. Service Discovery 6. Serialization 7. Synchronous Communication 8. Asynchronous Communication 9. Storing Service Data 10. Setting Up Service Deployments 11. Unit and Integration Testing 12. Security and Compliance 13. Maintenance
14. Reliability Overview 15. Collecting Service Telemetry Data 16. Setting Up Service Alerting 17. Performance Monitoring 18. Advanced Topics
19. Implementing Distributed System Scenarios 20. Advanced Topics 21. Other Books You May Enjoy
22. Index

Alerting best practices

The knowledge you will gain by reading this section should be useful for establishing the new alerting process for your services. It will also help you improve the existing alerts if you are working with some established alerting processes.

Among the most valuable best practices, I would highlight the following ones:

  • Keep your alerts immediately actionable: Alerting is a powerful technique to ensure any issues or incidents get acknowledged and addressed. However, you should not overuse it for the types of issues that do not require immediate attention. Some types of alerts, such as alerts indicating high saturation, are not necessarily actionable. For example, a sudden increase in CPU load may not indicate any immediately actionable issue, unless it remains high for some prolonged period (for example, CPU load not going below 85% for more than 10 minutes), and might just be a transient symptom of high service usage. When creating alerts, think...
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 €18.99/month. Cancel anytime