Monitoring seems to be very difficult these days. As development trends shifted to Microservices Architectures, applications were fragmented a lot, and the structure became more complex due to the use of asynchronous frameworks. As a result, it has become difficult to monitor complex applications in the event of a failure.

Traditionally, APM has been a system mostly used by developers and operators. This required more than a certain level of expertise, such as transaction analysis, failure analysis, and resource trend identification.

So this time in WhaTap VIEW from a business perspective, in other words 'Business dashboard'A new one has been introduced. This is a screen designed so that anyone with domain knowledge about their work can easily view it, even if they are not a developer or operator.

You can intuitively check how your domain application is working, how many transactions are being processed per second, and how many errors are occurring.

Also, the one introduced earlier Why is it important to design an API according to business design?As you can see in, many companies are systematically designing RESTful APIs, so WhaTap automatically assigns transaction URLs as a business unit based on the 1-depth of the URL by default so as not to set them manually. (Note, it is possible to express up to 2-depth.)

✅ Why is business monitoring important?

1. Recognizing business-oriented issues

For example, an order domain (/orders) If a failure occurs, it will directly affect the company's revenue. Even if the entire system works properly, if only the payment function fails, actual loss of revenue may occur along with customer dissatisfaction.

Also, authentication/authorization domains (/auth) If there is a problem, the customer will not be able to use the service because they can't even log in, which will soon lead to loss of business.

🔎 Business-oriented metrics such as “order failure rate,” “payment response time,” and “login success rate” are often far more important than simple system metrics.

However, in traditional monitoring, transactions are randomly mixed, so even if an actual failure occurs, it is often not possible to quickly recognize a really important failure.

To address these issues, WhaTap quickly identifies issues by domain and has established a business-based data system that supports rapid customer response.

2. Fast and accurate fault cause tracking

By monitoring on a domain-by-domain basis, you can immediately determine which features are causing issues.
For example, if you are in a situation where “I can't log in as a member, but I can't view products,” you can immediately recognize that there is a problem with the product domain.

If you're using an existing APM solution:

• Check whether a transaction error has occurred
• Analysis of transaction details (URL, response time, error class, error message, etc.)

This process is bound to take time to analyze various transactions individually.
However, it will take time to finally recognize that a failure has occurred in the “product” domain and take steps to prevent the spread.

👉 WhaTap's 'Business Dashboard' helps make this process much faster and more clear. If reminder conditions are set for each domain, notifications will occur when the following anomalies are detected:

• Rapid increase in error rates
• Response time delay
• A sharp increase or decrease in trading volume

Example: “The error rate for the product domain has exceeded 5%. Please check.”

This makes it possible to quickly identify problem domains, prevent the spread of failures, and respond immediately.

3. Essential elements in the MSA structure

In a microservices architecture (MSA) environment, a domain usually becomes a single service and an independent distribution unit.
e.g. order-service, payment-service, auth-service rattan

Therefore, if individual monitoring is not possible for each service, in the event of a failure

“The whole system is fine, what's wrong?”
Confusion like this is easy to occur.

In this structure, domain-specific and service-specific monitoring is essential.

4. Team responsibilities have been clarified

If your organization is divided into teams by domain, each team only needs to focus on monitoring the domain they are responsible for. For example, the payments team would only need to monitor payment domains.

However, some may ask:

“Is it enough to just look at the payment domain? How can I find out about external call errors during the payment process?”

WhaTap provides an answer to this. WhaTap provides a 'multi-transaction search' function, which can identify the following categories based on transactions executed in the payment domain:

• What SQL query was the problem
• Whether the external HTTP call failed
• Was there a problem with internal inter-system calls

Through this process, for example,

“Ah, there was a problem calling the AAA credit card company API.”
In this way, the cause of the failure can be clearly identified.

5. Metric-based improvements are possible

• “The order success rate is 92% yes? Why did it fall?” → Payment team identifies cause → Debug → Fix → Improve
• “The login failure rate is 5%? Why are there so many failures?” → Identify the cause from the auth team → Debug → Fix → Improve

🔎 With only technical indicators, this kind of analysis would be difficult. Try using Watab APM, which can monitor related businesses. Significant resource savings will be possible.

✅ How to use business dashboards

1. How to confirm business through business-specific and transaction-specific notification settings

• Set in the Alerts > Event Settings (new) > Transactions tab
  • Set up business alerts
    • The business name on the business dashboard is a large group organized based on the transaction's service name.
    • If a subtransaction alert is linked to a parent business alert, it may look like a failure even if it's not an actual failure.
    • To prevent this, it was developed so that business notifications and transaction notifications can be set separately.

• Set up transaction notifications
  • You can set notifications for each transaction URL (service).
  • You can filter by specific transactions.

2. How to view data through business dashboards

• Real-time anomaly detection function through the dashboard
  • Check transaction delays through business-specific active transactions
  • Check performance by task through response time trend graphs
  • Check the fault trend through the error trend graph
• History analysis function to detect past anomalies
  • View the total number of transactions per business
  • Estimating the point of failure through response time and error trends
  • Through detailed data, it is possible to check which traction for each specific business has many errors, whether the response is slow, and whether it uses a lot of memory

3. Real-time business confirmation through active transaction confirmation

• You can check business-specific transactions in real time.
• You can identify transactions that have not been terminated.
• You can check bottlenecks in transactions.

‍

corollary

More than simple system monitoring, business-specific monitoring is a key strategy to help identify anomalies directly related to revenue early and respond quickly. Learn more about business dashboards now.
👉 Learn more about the Watap Business Dashboard