Monitoring BizTalk Server
This section describes what's being monitored and the rules for how Nodinite translates this into meaningful monitoring states. Also, many remote commands are available as Actions to help you swiftly manage BizTalk related problems. Actions are further detailed in the Managing BizTalk Server page.
The agent auto discovers all your deployed BizTalk Server artifacts. Simply deploy new BizTalk Server applications and they will automatically be detected and get monitored and listed within your Monitor Views.
State Evaluation - Makes sure the BizTalk Server and deployed artifacts have the intended run-time state
If Nodinite can't check the state of your BizTalk Server, chances are no one else can either
Metrics - Provides graphs as both Actions and Widgets with run-time information, for example throttling (with thresholds for alerts)
Statistics - Helps you get insights about what BizTalk Applications fails with suspended messages, month by month
Health checks - Helps you keep your environment tidy and in sync. Provides some of the same features as the Terminator Microsoft support tool
- Nodinite Microsoft BizTalk Server agents make use of the Microsoft SDKs and offer you an automatic discovery of your BizTalk Server. Sharing and/or dividing access to any individual BizTalk artifact is very easy from within Nodinite.
Overview of one BizTalk Server group, also available as a widget on the Dashboard
- The Application name is based on the name from any given BizTalk Server Application:
- All artifacts of a given type belongs to an appropriate category The various monitoring capabilities for the BizTalk Server agent are expressed as Resources and are grouped by Categories. The Categories are unique for each Monitoring Agent.
The BizTalk Monitoring Agent also supports the execution of Remote Actions on most resources using the Nodinite Web Client tool or by programmatically calling the Web API. To execute remote actions some Prerequisites must be satisfied. The user must be logged on to Nodinite using a Windows Credential. The user must also be assigned a Monitor View with BizTalk Resources where Remote Actions are allowed. See Add or manage Monitor View for more details.
TIP: Users can be fine-tuned regarding assigned access (through the use of Roles and Monitor Views) to selected BizTalk artifacts on just about any level (everything, by selected applications, by selected categories or even individual artifacts)
* requires the use of the Monitoring Database
During root cause analysis or for other purposes it might be useful to understand how often problems with your BizTalk Server happens. If your Monitor View allows it, you can search for historical state changes for the provided time span either for all your BizTalk Server or individually. This topic is further detailed within the generic instructions on how to Add or manage Monitor View page.
Search for alert history for all resources in the Monitor View
Alert history for the selected BizTalk artifact
Other common problems and FAQ for the BizTalk Server Logging and Monitoring agent can be found in the troubleshooting guide