However we only find down alerts in the event viewer. We would also expect to get an Up Alert like we do with mails using "Log events to Event Viewer"

-By Jørn Justesen

The idea is to implement the filter Not Equals when searching in tracked data on the error code.
We have several places in our solutions where we terminate the instance, and we would like to easily search all these instances.
This functionality does exist in the BizTalk Administration Console, so basically we would like to have the same functionality (Errorcode != 0).

• Idea by Eldert Grootenboer

All the e-mails we receive from Biztalk360 are sent with "High Importance". is there a way to change that not sending with High importance?

By Jarkko Raback

Will be helpful if there is any audit trail on user management other than the last change to a user’s permission. In other words is the full history audited/recorded.

By Broer vos

The ability to do 'Terminate' on an instance should be controlled by permissions to make sure that not all users can do this. The consequences of terminating an instance which has ordered delivery enabled on it can be severe since all the messages 'in queue' are deleted when the instance is terminated. Some users should be able to do 'Resume' without have the rigts to do 'Terminate'

This is related to the configuration of BizTalk360 with ServiceNow. able to configure it successfully and incidents are coming in Service Now. But, I need the functionality like, I can create incidents and will be assigned to different groups based on the services from the BizTalk360 side.

In User Acces Policy you can give access for all Applications and for all custom queries.
I'd expect all Applications and all Custom queries will select everything from the table so you don't have to change this after adding an Application or a Custom Query.

Unfortunately this doesn't work like my expectation. So I have to change this for multiple user everytime an applicaton or a custom query is added.
And this happens many times because we have many Applications and new Applications are added almost every month.

We just want to publish the query results on the dashboard in tabular format. At this point we don't yet need fancy PowerBI graphical view of this data.

There is a limit of 50 attachments to download in Graphical Flow (Tracking).
Must there be a limit?
I suggest that max matches will set the upper limit, but to keep the configuration so it is possible to set the limit lower for those who need it.

In the Messaging Pattern list, if I click on a GUID for a not-named messaging pattern, I open the detailed view of the flow.
From here, if I want to rename the pattern, it is not possible... so I need to go back to the list, and search with the GUID and then rename it...
It could be much more convenient to renamed it directly from the graphical message flow.

Currently you are not able to view, edit, or delete Stop Alerts for Maintenance entries. I like to be able to enter Stop Alerts in the future for upcoming maintenance windows. We need to be able to view, edit, or delete those Stop Alerts.

Currently BizTalk 360 doesn’t support generic resubmission for Itinerary based solutions where the itinerary attached to the message in the ESB Exception database is resubmitted along with the message so that the message continues on at from the same step it previously failed at. This should be a general resubmission mechanism for all Itinerary based solutions.

When Message Box or Tracking queries return many results, it would be helpfull to have pagination to navigate through all the results

In the past BizTalk360 was tied to BizTalk MBV. Would like it tied to the replacement BIzTalk Health Manager now since MBV is being retired..

as per subject.

Ability to save msgbox queries, export then import to other envs (e.g. test to prod). Same for event viewer.
Custom sql queries, BAM, etc.

Currently when an alarm is created, we can enter the email ids to which the DOWN and UP alerts will be sent to. This is OK if the same recipients are targeted for both DOWN and UP alerts. However, if the alerts are sent to a support system that creates the tickets for the support team to action then we need ONLY the DOWN alerts to be sent to the support system. And configure separate email ids for the UP alerts (excluding support system) to avoid the creation of automatic tickets for UP alerts.

Currently BizTalk360 provides combined monitoring for BizTalk Servers under 'Managed Mapping'. As a result of this, if one server is shut down (for some maintenance work) , then either BizTalk 360 throws Threshold alert for the given schedule or We need to put BizTalk360 in 'Maintenance Mode'.
If we keep the seperate monitoring per server, then it will be maintenable and the unnecessary alerts can be avoided.