diff --git a/en/eBook/12.1.md b/en/eBook/12.1.md index 620b3670..06c43783 100644 --- a/en/eBook/12.1.md +++ b/en/eBook/12.1.md @@ -140,21 +140,23 @@ Above, we've defined and configured a custom log processing package. The followi logs.Logger.Critical("Server err:%v", err) } -## An error occurred mail +## Email notifications -The above example explains how to set up email, we adopted the following smtp configured to send e-mail: +The above example explains how to set up email notifications with `seelog`. As you can see, we used the following `smtp` configuration: -The format of the message through criticalemail configuration, and then send messages through other configuration server configuration, configured to receive mail through the recipient user, if there are multiple users can add one line. +We set the format of our alert messages through the `criticalemail` configuration, providing our mail server parameters to be able to receive them. We can also configure our notifier to send out alerts to additional users using the `recipient` configuration. It's a simple matter of adding one line for each additional recipient. -To test this code is working correctly, you can add code similar to the following one false news. But remember that after should delete it, otherwise you will receive on-line after a lot of junk e-mail. +To test whether or not this code is working properly, you can add a fake critical message to your application like so: logs.Logger.Critical("test Critical message") -Now, as long as our application online record a Critical information that you will receive an e-mail Email, so that once the online system problems, you can immediately informed by e-mail, you can timely processing. +Don't forget to delete it once you're done testing, or when your application goes live, your inbox may be flooded with email notifications. + +Now, whenever our application logs a critical message while online, you and your specified recipients will receive a notification email. You and your team can then process and remedy the situation in a timely manner. ## Using the Application log