Skip to content

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.

101 results found

  1. Data Monitoring File Size

    Would be nice to add additional Filter possibility, not only based on the number of file received, but also on the file size. At a customer site we have a WS Request that sometimes receives a wrong response. This response is much more smaler than the expected. Would be nice if I could configure an alarm if the file size is below a kb value.

    24 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

    Hi, Our latest version 10.8 introduces the capability to monitor the message size transmitted between the receive location and the send port. You can now configure the expected size in process monitoring, and if the message size violates the specified threshold configuration, it will trigger an alert. 

    Check out the release notes for more updates.

    Thanks,

    BizTalk360 Team

  2. Automation of disabling or stopping send ports and receive locations for scheduled outages, certain days of the week and hours.

    Automation of disabling or stopping send ports and receive locations for scheduled outages, certain days of the week and hours.

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

  4. Notification of orchestration instances which are active for more than 45 minutes

    Notification of orchestration instances which are active for more than 45 minutes using Data monitoring.

    by
    Azeef Kabeer

    15 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

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

  6. Web Endpoint Monitoring should have configurable 'pinging' interval

    We would like to check a web endpoint less often than once a minute to reduce overhead.

    10 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

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

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

  9. Email template

    To enable users to select any range of colors (RBG, HEX Values) so that the emails colors and templates can be customized per company styles…

    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

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

  11. Include event log message in notification email

    When a notification email is send for any event log violation like event id, event text etc currently it only shows a generic description saying event log alert triggered. It will be useful if you can include the actual text of the event, this will avoid user logging on into the BizTalk360 portal to see the actual message.

    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

  12. Send ESB Detail In Notification - Improvement

    When you activate the option “Send ESB Detail In Notification”, you are getting the data show below with the number of faults per Fault Code. This data is grouped by Fault Code which is the default grouping. I need the option to be able to choose the “group by” setting on one of the three fields: Fault Code (the default grouping now), Error Type or Exception Message. In the case below you need to group the errors on the Exception Message because this can be different for the same errorcode.

    ESB Fault Details in the application: Company.BizTalk.Application

    Fault Code: ESB0002,…

    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

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

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

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

  16. Consolidated View of Alarms in Monitoring Dashboard

    In the current version (8.2), the Monitoring Dashboard only displays one alarm at a time. In an organisation that configures many alarms, this means they can't see an overview in one screen of all mappings - unless they include an additional alarm that includes everything, which would cause duplicate emails, etc. Pretty sure that older versions of BizTalk360 included a consolidated view(?)

    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

  17. Show all receive locations, all send ports or all orchestrations for application monitoring in one overview

    In application monitoring I'd like to have the option to show all receive locations, all send ports or all orchestrations in one overview.

    This would make it much faster and easier to add all items in your monitoring.
    And this would also make it much easier to add new items in your existing monitoring or to do a weekly or monthly check whether all new items are added in your application.
    Now we have to click and reclick thousands of items if we want to check we have all items in our application monitoring. Especially when you have a lot…

    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

  18. Monitoring throttling conditions

    Currently you can visualize the health of your BizTalk environment throttling conditions using the "Throttling Analyser" feature, it will be good if we can have a mechanism to get notified if any particular throttling state remain active for a particular period.

    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

  19. Monitoring various queues like MSMQ, MQ Series, Azure Service Bus

    As part of the integration solution we will be using various queues like MSMQ, MQ Series etc, it will be nice if BizTalk360 can monitor some of the common queuing technologies that's available in the market.

    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

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

← Previous 1 3 4 5 6
  • Don't see your idea?

Feedback and Knowledge Base