It is not possible to end a data process monitoring at 12h00am (midnight). Let say we want to monitor 7h00pm until 12h00am, the web interface got an error: "The end time should be atleast 15 mins later than the start time.". We have to set 23h45 or 00:15. So it is impossible to get a result at 12h00am.
If we set 23h45, we don't have the last 15 minutes of the day included in the monitoring. If we set 00h15, the first 15 minutes of the new day is part of the new day, not the last day.

So our results are not exact if we take a look in the data monitoring dashboard.

New Message Box data monitoring tool – This new feature to perform actions is great allowing automatically messages to be resumed or terminated. The only issues with that is the minimum frequency we can set is only to 15 minutes and it would be perfect if we are allowed to set lower values like seconds or 1 minute for example. Also the option to send or not a notification for that as sometimes we don’t need the email and the last suggestion is to add the port name as a filter for that as sometimes we only would like to perform an action if the suspended instance is related to a specific port.

By Daniel Schnabel de Barros

We have quite a lot of servers, and thus quite a few artifacts we monitor. However, we have way more artifacts (NTServices, SQL jobs, etc.) that we do not monitor. But I notice these artifacts still add rows to the table b360alertMonitor_LogStateCheck (with ExpectedState 2). This gives us a lot of useless rows in this table for things we don't want to monitor anyway. Is there a way to turn this off? We now have 17 million rows in this table, and we only keep this data for a week (the cleanup job works fine).
I can write a job myself to delete these rows with ExpectedState 2 at a higher frequency than 7 days (more like every hour), but I was hoping there was an option to actually indeed 'do not monitor' them at all

By Marc van de Klashorst

We have incidents when BizTalk360 looses the connection to database because of network issues, during updates or maintenance windows. During those it have happened that the BizTalk360 service do not start, and I have no idea that the service was actually stopped until the customer (how manage the flow in the application) calls and says they aren't receiving e-mails.
We already have the IIS MP, so that are monitored. I asked my SCOM guy to create some rules (alerts) of the Event ID's I have found and monitoring the service.
But I would like to make a feature request to have and official SCOM MP (that are sealed) for monitoring the specific BizTalk360 components and events.

-Idea shared by Johan Ljunggren

The requirement is that the customer wants to receive an alert each time a message or instance got suspended. So this is a bit like an event driven approach.
Applications
Say you have an alert for Suspended Instances with a Warning threshold of (more than) 0 and an Error threshold of (more than) 5. This would result in getting a notification when:
a. nothing is suspended yet and
b. a Message or Instance got suspended
This is because the Warning threshold is set to (more than) 0. As far as I am aware of, the next notification you would get is when the Error threshold is met. So when this is set to 5, you would not get notifications of suspended messages/instances 2, 3 and 4.
Of course you have the 'If violation persists...' functionality, but when the 2nd, 3rd or 4th instance(s) got suspended outside that timeframe, multiplied by 'Limit Number...', you would not get a notification for the instances which occur outside that timeframe.
Data Monitoring
With Data Monitoring you could set the Data Filter to Suspended Service Instances and the Warning threshold to > 0, but when there are no suspended instances within the configured frequency you would get an email that no instances got suspended, which is a bit over-informative .
As far as my experience with Data Monitoring reaches, the closest you can currently get is a daily report with the number of suspended instances of that day, even when that's zero...
To solve this you could think of adding an Information Threshold which can be assigned a number, just like Warning and Error Threshold under Applications. When assigned:
- 0 no notifications will be sent
- 1 a notification will be sent for each suspended instance
- 2 a notification will be sent for every 2nd suspended instance
- 3 a notification will be sent for every 3rd suspended instance
- etc.
To prevent flooding the 'If violation persists...' / 'Limit Number...' functionality would apply.

• Idea shared by Lex Hegt.

I am configuring some Data Monitoring Alerts in BizTalk360 and have run into a snag. In my Test environment, we have crafted an ESB Exception for our Gibsons.FIN.Transactions BizTalk Application and have a Fault Category of ProcessCOACacheMisses. However when I am configuring this Data Monitoring alert in Production, I don’t have this Fault Category yet as it is a new application. I would imagine you are performing a DISTINCT SQL Query on the field and populating the dropdown with these values. It would be nice to override and provide my own text as now I have to wait for that alert in Production before I can configure the monitoring.

Not a huge deal as I will loosen my filters until the event happens but thought I would pass this feedback along.

By Kent Weare

Currently there is no place to see, at the same time, all artefacts that are set to autocorrect.

In BizTalk360 there needs to be one single view showing a live view of all artefacts that will autocorrect if they are down.

In this view, at least the following should show:
- Current retries and other per artefact settings related to autocorrect.
- Each artefact should have a link to the alarm view of the application.
- Each artefact should have a link to the operations view of the application.
- It should be possible to group artefacts in the view; for ex. Currently retrying, Per application, Per artefact type, etc.