The error message is usually the first hint to figure out what is causing the problems. BizTalk360 logs help to diagnose the errors that occurred in the BizTalk360 application. By configuring the logs, the system will collect all the error messages, which you can review by looking at the error description and timestamp.
Log Configuration
Some configurations must be completed as a first step in order to indicate to the system which logs must be collected. Say, If you frequently use the BizTalk360 monitoring feature and want to observe only monitoring problems, then you can enable logs to collect only monitoring errors.
Navigate to Environment settings->Administration->BizTalk360 logs and click 'Log Configuration'
In the configuration blade, update the log level and enable the feature lists.
The system will collect logs based on the log configuration and list them on the BizTalk360 logs page. The logs are listed along with the feature name, log type, server, description, and logged time. To review the log more in detail click on the eye icon.
you can filter logs based on log type, feature, server, and days to see only the required logs.
Only the super user can configure the log. The collected log details can be viewed by the superuser as well as anyone with access to a specific feature.
Acknowledge BizTalk360 Logs
In real-world environments, some errors / warnings are already identified and considered acceptable, so they don’t need to impact overall health of the environment. The Acknowledge Log option helps administrators to hide the known issues. Also the acknowledged issues will be skipped from the advisor score calculation and overall health consideration.
Consider a scenario where an enterprise integration environment handles high volumes of transactions between ERP and external partner systems. During peak business hours, occasional transient API timeouts may occur due to third-party system latency. These temporary warnings, while expected, can repeatedly appear in the BizTalk360 logs and negatively impact the overall health score.
With the acknowledge and suppression option, users can mark these known, non-critical warnings/errors as acknowledged, excluding them from Advisor score calculations and health status. Once the suppression period expires, acknowledged logs are automatically re-opened. And they are considered for advisor score and health status calculations in the next cycle.
Auto Suppression of Acknowledged Logs
Assume a scenario where an API timeout log is acknowledged and suppressed for a duration of 4 hours. If the same log occurs again within this suppression window, it will be automatically treated as acknowledged and excluded from Advisor score and health status calculations, preventing repeated impact from known, non-critical issues.
If users want to revert acknowledged logs, they can manually re-open them. Once re-opened, these logs will again be included in Advisor score calculations and health status evaluation.
If a log is acknowledged in one environment, the same log occurring in a different environment will not be considered acknowledged. Auto-suppression applies only to repeated occurrences of the same log within the same environment.
Purging
The collected logs are saved in the "dbo.b360_ev_logs" table of the biztalk360 database, which will be purged every 15 days. However, depending on your environment, you can increase or decrease the number of purge days. Purge policies can be defined under settings->BizTalk360 health->Data purging->BizTalk360 Logs.
