Monitoring

Azure Logic App

In the following example, we will configure an HTTP Event Transport from anynode to Microsoft Teams using Microsoft Azure Logic App. This integration allows events generated by anynode to be sent as notifications to a designated Teams channel or chat, providing real-time updates and actionable insights for improved system monitoring and management.

Log in to the Azure Portal.

Navigate to your resource group and click on Create.

Microsoft Azure resource group with create resources function.

Search for Logic App.

Click in Logic App on Create.

Microsoft Azure Marketplace overview with Logic App.

Select a hosting option. These hosting plans determine the resource allocation, scaling and pricing for your app.

In our example, we choose the Workflow Service Plan.

Click on Select.

Microsoft Azure with Logic App and hosting options.

Choose the Subscription, Resource Group, and a Name for your Logic App.

Select the Region closest to your services.

Click Review + Create.

Microsoft Azure with Logic App and basic settings.

You will get an overview with hosting details.

Click on Create.

Microsoft Azure with Logic App and review details.

Wait for the complete deployment.

This will take a few minutes.

Click on the Go to resource button.

Microsoft Azure with created Logic App and go to resource button.

Navigate to Get started and Create a workflow in Designer.

Click on Create workflow

Microsoft Azure with created Logic App and create workflow in Designer.

In the upper menu, click on Add and Add from template.

Microsoft Azure with Logic App and workflows with add from template function. .

Search for the template: Receive and respond to messages over HTTP or HTTPS.

Microsoft Azure with Logic App and workflows with template: Receive and respond to messages over HTTP or HTTPS

Click on Use this template.

Microsoft Azure with Logic App and template workflow for: Receive and respond to messages over HTTP or HTTPS

Enter a name for your workflow.

For the anynode-to-Teams workflow that involves user interactions (like Adaptive Cards) or where the workflow depends on external feedback or multiple steps, you should choose Stateful to ensure context is maintained.

Click on Next.

Microsoft Azure with Logic App and template workflow with basic settings.

You will get an overview of your settings.

Click on Create.

Microsoft Azure with Logic App and template details.

Click on Go to my workflow.

Microsoft Azure with Logic App and template details with go to my workflow button.

Navigate to Get started and Edit in designer.

Click on Get started.

Microsoft Azure with Logic App workflow edit in designer function.

Navigate to the flowchart and click on When a HTTP Request is received.

In the left menu, navigate to Parameters and HTTP URL.

Microsoft Azure with Logic App and template parameters.

The HTTP URL for the "When an HTTP request is received" trigger is a unique endpoint where your workflow listens for incoming HTTP requests.

The URL serves as a webhook endpoint. You can configure external systems (like anynode) to send HTTP requests to this URL when specific events occur.

Copy the URL, you will need it later in the anynode frontend (anynode event transport assistant with options for the HTTP request.).

The following action allows you to present an interactive Adaptive Card in a Teams channel or chat. Adaptive Cards are customizable message containers that can include text, buttons, dropdowns, images, or input fields.

Click on the upper plus to add an action.

Search for Post adaptive card and wait for a response.

Choose it.

Microsoft Azure with Logic App and workflow with added action: Post adaptive card and wait for a response.

Navigate to Parameters in the left menu.

Choose Flow bot as post.

At Post in, select Chat with Flow bot.

At Recipient, enter the mail address of a Teams user who will receive the message.

The Message field defines the content and layout of the Adaptive Card.

This is usually a JSON payload that specifies how the card looks and behaves. The message field uses the Adaptive Card schema, which can include:

• Text blocks: To display information.

• Action buttons: To let users respond (e.g., Approve/Reject, Transfer/End Call).

• Input fields: To collect user input like text, choices, or dates.

You can include parameters in the JSON to populate parts of the card with dynamic content.

We have prepared an adaptive card for you, which you can use for our provider node failure example.

Microsoft Azure with Logic App and workflow with added action parameters.

Delete the lower Response. Select it and navigate to the three points in the right parameters menu and click on delete.

Click on the Save button in the upper menu.

Microsoft Azure with Logic App and workflow with delete function.

Continue with the next chapter and create an HTTP event transport in the anynode frontend. After a successful configuration, you should get this message via Microsoft Teams:

anynode event notification via Microsoft Teams chat message.