In actual business, system business exceptions are often obtained passively. For example, when a certain function is not working through the business department or customer feedback, the system appears to be passive and dull.
In SpringBoot, there is unified exception handling that can be implemented. When we detect non-business exceptions, such as null pointer exceptions, array out-of-bounds exceptions, etc.
We can actively know the time and business scenarios when the exception occurs, so that the system can actively capture the exception and quickly locate and process it
But they have all encountered the same thing - system abnormalities lead to losses. This seems to be something every company has to go through
Regardless of whether it is the e-commerce industry or the financial industry, any business involving transactions will actually have great systemic risks. For example, if the system or interface is abnormal, the user cannot complete the transaction, which is a loss of transaction volume for the company. Another example is that improper operation of the operating personnel leads to being swiped or scammed, which is a loss of profit for the company.
When we usually develop interfaces, we encounter interface exceptions, and we hope to know as soon as possible
In the past experience, we have informed the corresponding personnel through emails and other means
Most alerts can now be sent to the relevant app
Group robot is an advanced extension function of DingTalk group. Group robot can aggregate the information of third-party services into the group chat to realize automatic information synchronization
With the help of DingTalk Robot, we can easily notify the corresponding personnel of abnormal alarm information by calling the official API