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.

  1. Maintenance Alarm Exclusions

    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'

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Existing Feature Enhancement  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Age-based monitoring for Data Monitoring

    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.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New Feature Request  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Schedule recurrent maintenance stops

    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.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Existing Feature Enhancement  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Disable group by error code in data monitoring "Send Instance Detail In Notification"

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

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Existing Feature Enhancement  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 'Do not monitor' option for Web Endpoints monitoring

    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.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New Feature Request  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Restrict alarms by user group

    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.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  New Feature Request  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Support SQL cluster monitoring

    When SQL 1 server went down and SQL 2 (clustering) starts running BizTalk Server starts capturing and running. But BizTalk360 still pointing to that SQL1 sever and keep pooping the message "Disks: Configured Disk . No longer exist in the Server XXXXXXX." we expect BizTalk360 should support SQL Cluster Monitoring.

    By Duane

    16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New Feature Request  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Allow for monitoring of 3 or more SQL instances, or include disk monitoring of BT instance by default

    Allow for monitoring of 3 or more SQL instances, or include disk monitoring of BT instance by default.

    By Default you can't Monitor the BT Instance Disks (Monitoring> SQLServer Instances > BT Instance Name)

    So you have to add it to Settings > Monitoring and Notification > SQL Servers for Monitoring

    This only gives you a maximum of two

    We have 3 SQL Instances relating to the BizTalk Environment including the BT one, so we have to choose to not monitor one of them.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Existing Feature Enhancement  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Displaying an Alarm Dashboard

    We set up several alarms for different dataflows we have in our BizTalk environment (with different time-schedules).
    We would like to setup the dashboard on a Big screen for monitoring-purposes. However switch between alarms in the dashboard is pointless in this situation. We would like to suggest an Alarm-dashboard which shows the status of all the alarms. This is a screen we can put on a big screen.

    • Idea shared by Joost Easton.
    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  New Feature Request  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Increase the limit of SQL server

    To increase the number of SQL servers in BizTalk 360 for monitoring

    By Simon Laverdière

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Existing Feature Enhancement  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Web Endpoint monitoring support TLS 1.2

    We have some WebServices that we want to monitor with Web Endpoint monitoring and those WebServices were recent changes to accept only TLS 1.2 connections.

    And it seems that BizTalk360 is not able to do the connection to those endpoints.

    By Niko Rissanen

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Existing Feature Enhancement  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Autocorrect should have configurable retry interval

    Currently autocorrect tries to enable a port once a minute. It would be nice to configure this to a different interval like once every 5 minutes.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  New Feature Request  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Create a Consolidated Alarms Monitoring Dashboard

    Having a 4th option on all the various monitors called Consolidated which would show each alarm tree under the previous one and not have an Alarm selector.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  User Interface  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Terminate the service instances older than XX hours through Automatic Actions in BizTalk360

    We have a need for functionality regarding the filtering by time range in Data Monitoring.
    We have a case where we are moving data from customer’s ERP to their CRM daily using BizTalk.
    And sometimes those transfers fail.
    If the transfer is older than 24h it already obsolete and we would like to get rid of that kind of BizTalk instances using the Data Monitoring.
    As far as I know there is no way to setup it a way where it would terminate the instance if the creation date is older than 24h from current time?
    The closest we have…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Existing Feature Enhancement  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Enabling/disabling SQL jobs

    Enabling/disabling SQL jobs is not supported from BizTalk360 portal? it would be great to include this feature.

    By Ming.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  0 comments  ·  Existing Feature Enhancement  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Monitoring clustered disks

    Right now BizTalk360 is able to monitor disk spaces in BizTalk and SQL servers, it will be useful to monitor clustered disks. At the moment if the disk failover to secondary server, 360 starts alerting.

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Azure ServiceBus subscription monitoring

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

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Existing Feature Enhancement  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. New feature requests on Autocorrect

    I have couple of new feature requests for BizTalk360.

    1. Receive Location/Send Port/Orchestration - Auto Correct (set time)
    2. Option to configure BizTalk360 to try to auto correct artifacts in scheduled time (every 1 hour 5 times).
    3. Use case: BizTalk Receive Location A goes in disabled state. BizTalk360 tries to auto correct Receive Location 5 times and fails to restart port. Alarm email is sent to monitoring person, but it is night time and person is not available to react on alarm email. Receive Location stays disabled until monitoring person comes to work etc. and activates Receive Location manually.
    4.    Solution: Set time
    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New Feature Request  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Sort by alphabetic order the

    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.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Existing Feature Enhancement  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Monitoring for Always On Instances

    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.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  New Feature Request  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base