Maintenance Alarm Exclusions

Currently Alarms to keep enabled during Maintenance is a 'global' setting across all Maintenance schedules.

Depending on the 'maintenance' being done alters the alarms that should stay active.

For example, Server Patching with reboots may have no alarms that are left reporting.
Whereas installing/updating various BizTalk applications alarms monitoring network/infrastructure of the environment would want to be left 'active'

Occasionally I find it necessary to disable specific data monitors while a specific process is down or temporarily on hold. I don't want to disable the entire associated Alarm, as that would impact more than wanted. Since there is no Disable/Enable feature, I am forced to delete and recreate the Data Monitor instead.

We use data monitoring mainly for measuring purposes (analytics) and not for guarding the environment/processes.
To keep everything clean (especially when filtering the data monitor results) we do want to combine them into the same alarms as we use for guarding thresholds on the servers/artifacts.
So we would like to be able to disable alarm-triggers on each/all data monitor, the monitor just has to measure and put the result in its dashboard.

Agreements in a party can get disabled, it would be great if we can perform auto start and monitoring on it.

When creating a Data Monitoring alarm, it would be great to be able to check for instances which are older than XX days/minutes/seconds.

For example : let's say we have 2 dehydrated (or suspended, or whatever) orchestrations, 1 created 3 days ago and 1 only 10 minutes ago. This feature would allow BizTalk360 to raise an alarm for instances that take too much time to complete, or suspended instances that have obviously been overlooked.

It is possible to stop the alerts for maintenance immediately or in the future.
But what could be very good is the ability to set up recurrent stop for alerts, for example, each sunday at 4AM for 4 hours.

To enable users to select any range of colors (RBG, HEX Values) so that the emails colors and templates can be customized per company styles…

Hi,
In the DataMonitoring DashBoard, when we click on a particular alarm in the calendar, it displays the detail in a pane that is opened at the right.
But when this panel is displayed, if we click on another alarm the detail of this alarm does not replace the one that is currently displayed.
And sometimes when we click on the alarm nothing happened, the detail is not displayed.

In order to setup real reports that can be sent to end users or technical super users with all errors given the time interval set in the monitoring details, there must be an option to disable the grouping by error code for "Send Instance Detail In Notification" option.

Example: An orchestration hits the suspend shape with different errors for the given process, each time the data monitoring alarm fetches these errors only the latest will be displayed in the notification as the suspend shape always gives the same error code (obviously).

Kindly introduce a new feature 'Do Not Monitor' in the 'Web Endpoints' section so that we can make the web endpoints active / inactive on need basis.
Currently we dont have any option but to remove the endpoint in case of any issue.

When defining alarms it should be possible to separate alarms by "user group". Essentially we will be sharing access to BT360 with our client and we would like them to be able to create their own alarms for their applications. However we don't want them to be able to edit (or delete) our alarms. It should be possible to separate alarms by user group.

When SQL 1 server went down and SQL 2 (clustering) starts running BizTalk Server starts capturing and running. But BizTalk360 still pointing to that SQL1 sever and keep pooping the message "Disks: Configured Disk . No longer exist in the Server XXXXXXX." we expect BizTalk360 should support SQL Cluster Monitoring.

By Duane

Allow for monitoring of 3 or more SQL instances, or include disk monitoring of BT instance by default.

By Default you can't Monitor the BT Instance Disks (Monitoring> SQLServer Instances > BT Instance Name)

So you have to add it to Settings > Monitoring and Notification > SQL Servers for Monitoring

This only gives you a maximum of two

We have 3 SQL Instances relating to the BizTalk Environment including the BT one, so we have to choose to not monitor one of them.

We set up several alarms for different dataflows we have in our BizTalk environment (with different time-schedules).
We would like to setup the dashboard on a Big screen for monitoring-purposes. However switch between alarms in the dashboard is pointless in this situation. We would like to suggest an Alarm-dashboard which shows the status of all the alarms. This is a screen we can put on a big screen.

• Idea shared by Joost Easton.

To increase the number of SQL servers in BizTalk 360 for monitoring

By Simon Laverdière

We have some WebServices that we want to monitor with Web Endpoint monitoring and those WebServices were recent changes to accept only TLS 1.2 connections.

And it seems that BizTalk360 is not able to do the connection to those endpoints.

By Niko Rissanen

Currently autocorrect tries to enable a port once a minute. It would be nice to configure this to a different interval like once every 5 minutes.

Having a 4th option on all the various monitors called Consolidated which would show each alarm tree under the previous one and not have an Alarm selector.