Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Serverless Integration Design Patterns with Azure

You're reading from   Serverless Integration Design Patterns with Azure Build powerful cloud solutions that sustain next-generation products

Arrow left icon
Product type Paperback
Published in Feb 2019
Publisher Packt
ISBN-13 9781788399234
Length 494 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Abhishek Kumar Abhishek Kumar
Author Profile Icon Abhishek Kumar
Abhishek Kumar
Srinivasa Mahendrakar Srinivasa Mahendrakar
Author Profile Icon Srinivasa Mahendrakar
Srinivasa Mahendrakar
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Serverless Integration with Microsoft Azure FREE CHAPTER 2. Azure Functions and Enterprise Integration 3. Introduction to Azure Event Grid 4. Azure API Management 5. Azure Service Bus with Integration Services 6. Introduction to Logic Apps 7. Control Flow Actions and Custom Connectors 8. Patterns with Azure Integration Services 9. B2B/EDI Solutions for Enterprise Integration with Azure Logic Apps 10. Hybrid Integration, BizTalk Server 2016 and an On-Premises Data Gateway 11. Intelligence in Integration Using Azure Cognitive Services 12. DevOps for Azure Integration 13. Monitoring for Azure Integration 14. Other Books You May Enjoy

Sending notifications of issues or events

Besides deciding what you want to monitor, you also must think about who should receive notifications about any issues or events. When using a monitoring product, email is often the first choice for sending notifications. However, monitoring products exist that enable you to send notifications via products such as Slack, ServiceNow, SMS, and so on. This can be helpful if you want to send these notifications directly to stakeholders or resolution groups.

Typically, IT personnel will receive these notifications first, after which they can take the appropriate actions. To divide the workload and based on the complexity of the issue, different notifications can be sent to different layers of the IT department. You can consider the following division as a starting point:

  • First and second level support: Receive issues that are repetitive and...
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