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.

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.

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.

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.

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…

Please add the ability to monitor ServiceBus subscriptions (active and deadletter) like it is already possible for ServiceBus queues.

Currently we have setup a datamonitoring for most of our external FTP partners as like a HeartBeat mechanism. However some our partners are not that amused if we connect every 2 minutes to their FTP environment.

Therefore would it be great if we additionally could specify the interval when a check should be done.
IE not the just the number of second, but a set like every 15/30/60 minutes etc!

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.

Hi,
When defining a new process monitor, the list of receive locations or send ports should be sorted in the alphabetical order and/or it could be great to have a search filter.

There is no widget in the operations dashboard to notify any kind of errors or warnings determined in the monitoring area. Knowing how many mappings and data monitoring is set up is more useful if you know what is actually wrong

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).

In the NT-Service monitoring I would like the option to make an alert for the startup-type. So we can quickly discover a wrong startup type.

Hi,
When we monitor a lot of artefacts and after an import of an alarm exported from another environment, we have sometimes a lot of orphaned items.
It could be very helpful to have, in the import process, a way to remove all orphaned at the same time. Otherwise, we need to go into each application, go on send ports/receive ports/orchestrations, ...

With BizTalk 2016 you have the possibility to configure the DB with Always On. Because of MSDTC you have to create at least 4 instances and to create the BizTalk Db in these instances. At the moment in BizTalk360 you can only monitor 2, this should be now changed to allow a better control of all bts DB.

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.