Manage Mapping
- 26 Nov 2021
- 1 Minute to read
- Print
- DarkLight
- PDF
Manage Mapping
- Updated on 26 Nov 2021
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
After you have created an alarm, the next step is to associate the components you want to monitor to that alarm. This process is called Manage Mapping. The Manage Mapping section in BizTalk360 contains all the components that can be monitored. Check the below list to understand what components can all be monitored:
- Applications - BizTalk application artifacts like Receive Locations, Orchestrations, Send Ports, Send Port Groups, and Service instances
- Azure Services - Monitor Azure Logic Apps and API Apps
- BizTalk Environment - Monitor Host Instances, Host Throttling, Web Endpoints, Database Queries, and BizTalk Health Monitor
- BizTalk servers - Monitor Disk space, System Resources (CPU, Memory), Event Log entries, and NT services
- File Locations - Monitor File shares, FTP sites, FTPS sites, and SFTP sites
- Queues - Monitor MSMQ queues, IBM MQ queues, and Azure Service Bus queues
- SQL servers - Monitor Disk space, System Resources (CPU, Memory), Event Log entries, and NT services
- SQL Server instances - Monitor the SQL Server Agent jobs
- Server availability - Monitor BizTalk Server and SQL Server availability
Was this article helpful?