Suspended Instances
Unlock actionable insights and drive smarter decisions by leveraging historical data on BizTalk suspended instances. Nodinite empowers you to proactively manage and resolve issues, ensuring seamless business operations.
This image displays the 'Suspended Instance' resource as seen in a Monitor View, indicating a healthy state.
Category Name = "Health Check"
Resource Name = "Suspended Instance"
What is the Suspended Instance Resource?
The Suspended Instance resource provides historical statistics and trend analysis for BizTalk suspended instances over the last 6 months. Unlike traditional monitoring resources with thresholds, this acts as a reporting portal, giving you access to month-by-month breakdowns grouped by BizTalk Application.
When to Use Suspended Instance Reports?
- Continuous Improvement Initiatives – Track trends over time to identify problematic applications and measure improvement efforts
- Root Cause Analysis – Identify which applications generate the most suspended instances
- Capacity Planning – Use historical data to predict infrastructure needs and resource allocation
- Executive Reporting – Provide hard facts and metrics to stakeholders demonstrating system health and improvement progress
- SLA Compliance – Monitor suspended instance patterns to ensure service level agreements are met
Why Use Suspended Instance Statistics?
Prove Hard Facts – Replace anecdotal evidence with concrete month-by-month data showing exactly which applications are causing issues
Drive Continuous Improvement – Establish baselines, set targets, and measure progress objectively with quantifiable metrics
Historical Context – Six months of data reveals patterns, seasonal trends, and the impact of system changes
Accountability and Ownership – Clear attribution by BizTalk Application enables teams to take ownership of their integration health
What's being evaluated for 'Suspended Instance'?
The 'Suspended Instance' resource in the BizTalk 'Health Check' Category acts as a placeholder, allowing you to access detailed reports using the Actions button. No thresholds are set, so you always have access to up-to-date statistics for informed decision-making.
The evaluated states are summarized below:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of 'BizTalk Suspended Instances' is not possible due to network or security issues | Review prerequisites | |
| OK | Placeholder | This resource is always OK; no editable thresholds exist | Details |
Tip
You can reconfigure the evaluated state using the Expected State feature on every Resource within Nodinite.
What remote actions are available?
- Details - View the report
- Edit thresholds - Not used
- Metrics chart
This image shows the available remote actions for the Suspended Instance resource.
Details
This is the main attraction – Access comprehensive month-by-month statistics that prove hard facts and drive continuous improvement initiatives.
Click the Actions button, then select the Details menu item to open the statistics report for suspended instances:
Example: Details Action.
A modal opens.
This image shows the statistics report modal for suspended instances, grouped by BizTalk Application name.
Month-by-Month Breakdown
The report presents statistics for suspended instances from the last 6 months, grouped by BizTalk Application name and sorted by the total number of suspended instances (descending). Each column represents a different month, allowing you to:
- Track trends – See if suspended instances are increasing or decreasing over time
- Identify problem applications – Quickly spot which BizTalk applications generate the most suspensions
- Measure improvement efforts – Quantify the impact of fixes, upgrades, or process changes
- Prepare executive reports – Export hard data showing system health and reliability metrics
The header highlights the oldest still suspended instance (which may be older than 6 months if not properly managed) and the originating BizTalk application. This critical metric helps identify long-standing issues that require immediate attention.
Export to CSV
Click the Export to .csv button in the top-right corner of the Details modal to download the raw data for further analysis.
The exported CSV file contains detailed, granular data with the following columns:
- Application name – BizTalk application that generated the suspended instance
- Oldest (UTC) – Timestamp of the oldest suspended instance in UTC
- Oldest (Server time) – Timestamp of the oldest suspended instance in server local time
- Error code – Hexadecimal error code (e.g., 0xc0c01680)
- Service name – BizTalk service or orchestration name
- Count – Number of suspended instances for this combination
- Year – Year of the suspended instance
- Month – Month number (1-12)
Use the exported CSV to:
- Create custom reports – Import into Excel, Power BI, or Tableau for custom visualizations and dashboards
- Perform trend analysis – Calculate month-over-month changes, identify seasonal patterns, and forecast future issues
- Share with stakeholders – Distribute raw data to development teams, management, or external auditors
- Archive for compliance – Maintain historical records for SOX, HIPAA, or other regulatory requirements
- Deep-dive troubleshooting – Filter by error code or service name to isolate specific failure patterns
Tip
The CSV export provides granular data broken down by application, error code, and service name for each month. This level of detail enables root cause analysis that goes beyond the summary view in the UI.
Metrics chart: Metrics
All Suspended Instances are visualized in a single graph using the Metrics feature of this agent.
- Metrics
- Today – Active
- Today – Aggregated
This graph shows the active number of suspended instances.
This graph shows the aggregated number of suspended instances.
Note
To use this feature, an Administrator must manually enable it using Remote Configuration.
Edit
❌ The Edit action is not practically available for the Suspended Instance resource.
Click the Actions button, then select Edit to see the edit dialog:
Example: Edit menu item.
The modal opens:
The edit dialog displays the message: "This view is not available yet for the resource 'Suspended instances'."
Because the Suspended Instance resource functions as a reporting portal rather than a traditional monitoring resource, there are no thresholds or configuration settings to edit. The resource is designed to always remain in an OK state, providing uninterrupted access to historical statistics and reports.
Tip
This design ensures you always have access to suspended instance statistics for continuous improvement analysis, regardless of current system state.
Next Step
Add or manage a Monitoring Agent Configuration
Configuration