Introduction

This article explains about End to End Monitoring and alerts in Webmethods.io integration

Audience

It is assumed that readers of this article know how to create workflow and integrations on Webmethods.io integration.

Prerequisite

• Create Integration on FlowEditor
• Create workflow and invoke FlowEditor integration.

      Artifacts created

• Create FlowEditor service named as GetAccountData

1174×354 50.9 KB

• Create Workflow name it as AccountService.
• Invoke the FlowEditor Integration within workflow.

1053×356 38.1 KB

• Navigate to End to End Monitoring using App Switcher
• Overview provides the Total transaction count with their individual status
• Topology provides pictorial representation of flow of transaction

1909×574 101 KB

• Create the group on the dashboard of end to end monitoring.
• This group will bundle all the request for a particular transaction.

• Provide the group Name as Accounts
• Select products for which monitoring needs to be done
• Give the transaction name as your flow service name

738×658 49.8 KB

• Navigate to Alert and click on Rule list
• Click on create rule

969×744 42.1 KB

• We create the rule on key performance indicators (KPI)
• While creating rule 3 options are provided for KPI

• KPI on Error Count
• KPI on Error rate
• KPI on Average response

960×729 57.3 KB

• In this case KPI is set on Average response time.
• Configure the email ID in the recipients to get the notification.
• As per the rule, Email will be sent if average response time is greater than 10ms.

987×755 54.4 KB

968×759 49.7 KB

• Navigate to Webmethods.io workflow
• Trigger the workflow.

1186×394 47.7 KB

• Navigate to End to End monitoring.

1028×342 28.2 KB

• Click on Accounts

1647×390 50.2 KB

• Select GetAccountData

1484×511 115 KB

1915×727 85.6 KB

• In this case email is sent as transaction took more than 10ms to complete.

1545×820 90 KB