BizTalk360 - Monitoring
We love your feedback and look forward to hearing from you. A great place to post your ideas and vote up others. Please share your stories to help us build a product that best fits your needs.
Please note this site is only to get future ideas and suggestions. If you have any technical challenges with the current version of BizTalk360 please use our support site
You can provide any ideas/suggestions related to improving BizTalk360 monitoring capabilities in this forum.
51 results found
-
We would like to see auto correction action to be coorelated to the monitoring interval
We would like to see auto correction action to be corelated to the monitoring interval
6 votes -
Monitoring dashboard improvements on green /red lights
The test was to stop IIS. Simulation of web server crash, malfunction or network error. We performed an IIS Stop service only. No stop of biztalk360 service.
The results: The client browsers keep having the service status green flashing light at top right corner of the Dashboard monitoring portal. And the monitoring icon on the top left turned red saying that the service monitoring service is stopped (which is wrong).
So, on the upper left (blue left panel with the menu), that a red light appeared beside the icons monitoring and analytics. The red light beside monitoring is saying that…
2 votes -
Data monitoring with arbitrary interval
I've been informed by BizTalk 360 support that BizTalk 360 currently does not support data monitoring with arbitrary interval, say 7.5 days(180 hours). It would be nice to have this enhancement.
2 votes -
Data monitoring dashboard need to be listed according to monitor names
Currently Data Monitoring dashboard monitors are listed as per processed time. Where the data monitoring dashboard needs to be listed according to the monitor names.
By Mike Walsh
1 vote -
Auto-correct email improvements
Autocorrect feature works correctly but the auto correction email message displays “Critical” status in the summary. The summary message should display the final correction status along with prior status.
Also, the auto correction fix message displays under the “Issues of application name”. There should be new paragraph saying “Issues fixed:”
By Nitin C.Narkar
1 vote -
Filtering capabilities in Alert History
From time to time I find myself wandering through the Alert History. At that times I often miss the capability to:
Being able to see all records in the Alert History.
Have filtering capabilities like we know from Message Box queries and Graphical Flow.
Being able to show the actual mail which is being sent (I noticed this is in the database).By Lex
1 vote -
Preview Facility for Data Monitoring Filters
While mapping a MessageBox data monitoring to an Alarm, SQLDataFilter section does not have a Preview query option. Having a preview option is good in terms of being definitive about functionality of the monitoring. It does depend on availability of the correct data in message box. But considering the fact that these kind of alarms are set reactively than proactively, it will be nice to have Preview option.
1 vote -
Monitoring Free disc Space in GB's
Currently it is possible to monitor free disc space in percentages. It would be handy if monitoring could be done based on free GB's
2 votes -
Create platform alert mappings for all BizTalk nodes at once
When you have BizTalk Enterprise with multiple BizTalk nodes and want to create a platform oriented alert, there are topics like available disk space and event log entries, which you have to create for every node of the BizTalk Group. It would be helpfull if you can create this kind of mappings for all BizTalk nodes at once.
2 votes -
Bulk update for the max number of attempts for autocorrection
It could be great to have the ability to change the max number of attempts for autocorrection in a bulk way.
3 votes -
Date/time of error/warning occurrence in 'Errors and Warnings' overview
Currently when errors or warnings are displayed you have no direct clue when this has occurred. Some errors will stay in the monitor, even when the issue has been resolved.
No you have to check and in most cases need to conclude that it is an 'old' error/warning.1 vote
- Don't see your idea?