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.

How can we improve BizTalk360 Monitoring capabilities?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

2 results found

  1. SQL Server Instance monitoring

    The requirement is to ensure that a specific instance (e.g., SQL1) remains active, and to receive a notification if the active instance switches to another server (e.g., SQL2 or SQL3).

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    planned  ·  2 comments  ·  New Feature Request  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. Enhanced Logic Apps Support in BizTalk360 — Self-Healing for Standard Logic Apps

    Self-Healing / Auto-Corrective Actions for Standard Logic App Run Failures

    Current State
    Auto Correct for Logic Apps today only handles state changes — if a Standard Logic App gets disabled, BizTalk360 re-enables it automatically. No further corrective actions are available.

    The Gap
    When a run fails due to connector timeouts, API errors, or bad triggers, BizTalk360 can alert via metrics monitoring but cannot act on it. Manual intervention is still required.

    The Ask
    Extend automated corrective actions to Standard Logic Apps for run failures. When the "Runs Failed" metric crosses a defined threshold, BizTalk360 should automatically retry/resubmit the failed run…

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  New Feature Request  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?

BizTalk360 - Monitoring

Categories