Unifying notification formats

What is wrong with the old way

Notifications in WhaTap can occur in a variety of situations. We provide information specific to each situation based on the platform being monitored, the type of alert, and the channel through which the alert was received. However, with so many different types of alerts, it was difficult to understand at a glance what information was important when you received an alert.

The solution

As of April 20, 2022, WhaTap services will provide the following types of notifications. (SaaS service only) The main objectives of this update are as follows.

Provide as much information as possible in a consistent format regardless of ① platform, ② notification type, and ③ notification channel!

Examples

The photos below are examples of notifications that can occur in the WhaTap service.

Log monitoring real-time email notifications

Application monitoring (language: JAVA) real-time notification changes

Application monitoring real-time messenger (Slack) mobile notifications

Server monitoring messenger (Slack) notification example

Server monitoring mobile messenger (Slack) notification example

Notification title

As you can see from the three examples, all notifications have the following subject lines.

1.Notification title format

[Level][Platform][ProjectName][ApplicationName][EventTitle]

Notification message

Previously, the same kind of notification could have different information available for different notification channels. To compensate for this, we have organized the messages to include as much information as possible that can be provided when each notification occurs.

The values that can be in a notification message can be found in [ Common notification template guide - Event messages ].

Types of notifications where the user does not specify the notification subject and message

Application alerts and server alerts (e.g., server alerts, server process alerts, log file/window events) do not allow users to specify the subject and message of the alert. This made it difficult to know with what subject and message when a notification was raised. Conversely, if a notification was raised with a subject that was not specified by the user, we had to guess which notification setting caused it to be raised.

To compensate for this, we added an alert type to the alert message. In the example below, the notification type is SERVER_LOG_FILE, so you can see that the notification was triggered by the "Notify me of log files on the server platform" setting. You can learn more about the types of alert types in the [ Common alert template guide - Event messages ].

[Critical][INFRA][Production ServerINFRA Monitoring][ip-10-20-3-226][LOG File: , Keyword : , [Event] May 12 07:14:00 ip-10-20-3-226 zed: eid=208 class=config_sync pool='yardbase']... Omit ...Notification type : SERVER_LOG_FILE... Omit ...

Additionally, for notifications where the user specifies the notification subject and message, we have created a subject and message guide for each notification type to help you understand what subject and message notifications are sent with.

If you need to update this feature in your install, please contact support@whatap.io and we will help you.