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. 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. Data monitoring could not ended at midnight

    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…

    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

    0 comments  ·  Bug  ·  Admin →
  3. Data monitoring custom time

    New Message Box data monitoring tool – This new feature to perform actions is great allowing automatically messages to be resumed or terminated. The only issues with that is the minimum frequency we can set is only to 15 minutes and it would be perfect if we are allowed to set lower values like seconds or 1 minute for example. Also the option to send or not a notification for that as sometimes we don’t need the email and the last suggestion is to add the port name as a filter for that as sometimes we only would like to…

    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

  4. Don't save results for 'Do not monitor' artifacts

    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…

    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

  5. API to create/update an alarm

    Is there an API available that will allow me to create/update an alarm?

    We have built a .Net based deployment tool that takes care of all of our deployments and it would be good if we could tie in the Alarm create/update for new artefacts as part of this process.

    By Patrick Smith.

    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

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

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

  8. Certain receive location disabling on weekend

    The requirement is to have a certain receive location to be disabled on weekends. BizTalk only has everyday ability for this.

    Idea shared by Kada Dunn.

    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

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

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

  11. Message content In ESB data monitoring

    Capability to attach the message content for ESB data monitoring like Suspended Messages.

    By
    Eric Abts

    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

  12. Send events to ServiceNow Event module

    The Event Module for ServiceNow is a part of “Service Monitoring”.
    This enables correlation of events and alerts from a number of monitoring systems to view Business and Service Impact
    Grouping Event->Alerts (correlation) using AI (Machine Learning) to predict Incidents.
    Suppressing Events (Incidents) during change and maintenance.

    We would like to have the possibilites to send events from BTS360 to ServiceNow event module.

    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

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

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

  15. Attached file to Alarm Mail

    It would be nice for Invalid files (not validated in the incoming pipeline) or suspended, that you could choose to add the file to the alarm mail sent.

    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

  16. Add option to check FTP connection every specific period

    Currently we have setup a datamonitoring for most of our external FTP partners as like a HeartBeat mechanism. However some our partners are not that amused if we connect every 2 minutes to their FTP environment.

    Therefore would it be great if we additionally could specify the interval when a check should be done.
    IE not the just the number of second, but a set like every 15/30/60 minutes etc!

    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

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

  18. Widget with errors

    There is no widget in the operations dashboard to notify any kind of errors or warnings determined in the monitoring area. Knowing how many mappings and data monitoring is set up is more useful if you know what is actually wrong

    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

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

  20. Alert for wrong startup type from NT-Service

    In the NT-Service monitoring I would like the option to make an alert for the startup-type. So we can quickly discover a wrong startup type.

    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

  • Don't see your idea?

Feedback and Knowledge Base