Press enter to see results or esc to cancel.

Enabling Logging to Nodinite in Azure Logic Apps [Hybrid Scenario Series Part 2]

NOTICE: Nodinite does not require you to make any changes your Azure Logic Apps – no custom connectors needed! Also, Nodinite does not come with any restrictions on how many workflows you can log messages from or monitor. 

Nodinite enables you to centralize documentation, logging and monitoring for your workflows and system integration solutions for all system integration platforms. We at Nodinite have built-in support for many platforms, such as Mule ESB, Microsoft BizTalk Server, Microsoft Azure Logic Apps, IBM, etc and we are continuously developing support for more platforms. Using the API:s you are free to add custom code for your custom solutions to make sure you get self service from end to.

In this technical blog post we will cover how to log messages using Nodinite in your Azure Logic Apps. This is part of a series of blog posts in which we will cover “how to enable end-to-end logging and monitoring of hybrid integrations – end to end”.

Azure Logic Apps are key in Microsoft Azure’s integration services while building integrations in Microsoft Azure. Together with Azure Functions, API Management they are a powerful integration engine enabling consumption based integrations that are highly flexible at low cost.

Before we start

To follow this tutorial, make sure that you have the following:

  1. A working and running Azure Logic App in your Azure Subscription
  2. A running instance of Nodinite (if you do not have a running instance, get in touch with us and we will provide you with a time limited demo environment for free)
  3. The Azure Logic Apps Agent for Nodinite installed and an application in your Azure AD for Nodinite (you will need the client id and client secret while configuring the agent) – please follow this guide to do so: https://documentation.nodinite.com/Documentation/InstallAndUpdate?doc=/Troubleshooting/Azure%20Application%20Access

And also, it would be good for you to have

  1. An understanding on how Nodinite works – you can read more on our documentation. Or get in touch with us!

Configure the Agent

Before you start to configure the agent, please make sure you have followed this guide: https://documentation.nodinite.com/Documentation/InstallAndUpdate?doc=/Troubleshooting/Azure%20Application%20Access

For Nodinite to get all messages from your Azure Logic Apps, we need to configure the Azure Logic Apps agent.
This requires you to provide the agent with the following properties:

  1. Tenant ID
  2. Subscription ID
  3. Client ID
  4. Client Secret
  5. Resource Group – In Nodinite you need to specify all resource groups in which there are Logic Apps that you want to enable logging for

To enable logging to Nodinite, the “Enable logging” checkbox needs to be checked. If not, no messages from your Logic Apps will be logged to Nodinite.

Depending on the number of Logic Apps you have in your resource groups, this can take some time to get Nodinite in sync with your Logic Apps. Nodinite gets all runs that are still accessible in your portal – usually up to 30 days, depending on the configured retention time configured.

And you know what? That’s it! Azure Logic Apps agent for Nodinite does not require you to change anything in your Logic App – no custom connectors, no changes in your integrations, no nothing – except to register an application in your Azure AD.

End-to-end Logging

For this scenario, we are using a demo application, which exposes an HTTP endpoint that a web application is using to register users.

In the flow above, a message is received and a condition evaluates the request, either returning true or false. If the condition returns true, the flow is being terminated, if it returns false the user is being inserted into a Azure Storage Table. Also, since the user might be in the database already, the “Insert Entity” may fail. Depending on whether the user is in the database already or not, different status codes are being returned to the client calling the HTTP endpoint.

Azure Logic Apps agent for Nodinite logs all events and messages in Logic Apps. Each action has two events, pre-action and post-action. Depending on the amount of actions in your logic apps, the amount of logged events and messages differ. But at Nodinite we see this as a necessary part of a successful logging strategy. We need as much data as we can to understand the different system integrations. (And do not forget, Nodinite automatically obfuscates and compresses all data) And since Nodinite has self-service views you can decide which events you want to see in your search results. Read more on Log Views here.

To make sure to follow a message from A-Z, we use Azure Logic Apps built-in client tracking id to enable end-to-end logging. This ID is either created automatically or part of a Service Bus message or an HTTP endpoint (x-ms-client-tracking-id) and is sent to all steps within your Logic Apps (functions, connectors, etc.).

Nodinite will set the client tracking id as Nodinite’s built-in message property “System Interchange Id” and also part of the messages’ contextual properties.

Since it is a built-in message property, the “System Interchange Id”, we can (without the need of setting up a new Search Field) group search results by it and see single Logic Apps runs in Nodinite.

The Nodinite agent for Microsoft Azure Logic Apps provides us with all insights we need to understand the sequence of actions that run. Also, Nodinite logs all meta properties you can see in your Azure Portal.

Conclusion

Enabling logging to Nodinite in Azure Logic Apps is simple and requires no changes in your Logic Apps and enables you to

  1. Log all Logic App runs into one single platform
  2. Create self-service views for your organization to track data easier
  3. Using the client tracking id we can trace a message from A-Z, no matter if you are running a single Logic App or several, since the property follows along all logged messages
  4. Spend the time and money in the right place, since we are not requiring any changes in your Azure Logic App!
  5. Centralize all your logging needs, we support logging from BizTalk among other plattforms and for us, it really does not matter.

Did you know that the Nodinite supports monitoring your Azure Logic Apps? You can read more on all of the capabilities we offer for Azure Logic Apps here. Making it one single plattform for your monitoring, logging and documentation tools!

And do not forget to look at a complete list of our agents over at our documentation.

if you want to learn more, get in touch with us and get your personalized demo of Nodinite here.

Comments

Leave a Comment