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.

Suspended messages are routed to ESB and for some reason doesn't reach ESB, in this case user wants a notification
but problem is if you search in suspended messages there are too many and the suspended message application name does not reflect the application from which the message came - the application name of the suspended message is All.Expcetions
You need to go into the message context of suspended message & read the application name there.
Currently a powershell script is used to filter the applications in message context.
Basically can BizTalk360 go thru the message context and read the message application name as the suspended message application name is different

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.

Inspired by some of the sessions at Integrate2017, I suggest you analyse the possibilities to develop an “Assign to me” function. Let me describe a bit more…

An alert-email goes out as a Biztalk send port is down. This email goes to a group, in our case 6 recipients. Then, who’s going to fix this? Maybe there could be a button in the email and when I click it, the status in 360-db on this alert goes to “ongoing work”/”under investigation” or something like that, with my ad-name as responsible. Then, another email goes out to the group as the status has changed and everyone knows that someone in the group is working on it.

Hope I made my point understandable, otherwise, just send an email and I’ll try to describe in other words…

Best regards,

Tom Nyberg

I am needing the capability to route suspended message ‘Data Monitoring’ notifications to some IT partners, but, based upon information that is in ONLY available in the Message Context. In these cases, the BizTalk messages are suspended with an Application Name of “Microsoft.Practices.ESB”, but are not able to make it to the Exceptions Portal and only associating the root application that caused the issue in the Message Context, which is how today we manually review and manually notify the development groups that these types of Suspended Messages occur. What I need is the capability to search generically across all Context Data elements, not just one if that eases the solution, using something like a SQL “like” wildcard.

• Idea shared by Eric Abts

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