Operations | Monitoring | ITSM | DevOps | Cloud

Many companies like all their API calls to external services routed through Azure API Management (APIM). If you are a user of Serverless360 BAM, then one of the options is to use Azure API Management as a proxy to your BAM API and then use APIM from within Logic Apps.

This blog will brief on vital ways to regain control of Azure cloud cost and to achieve cost optimization. To start with, let us have a short introduction about Azure cost management. As the growth towards cloud adoption is increasing in enterprises, it is getting more difficult for enterprises to manage the cost spent on the cloud across the organization.

Sometimes it may not be easy to debug Azure Functions deployed on Azure since we cannot do inline debug through the Azure Portal. An option for us is to write information to the Logs console in key parts of our code to get insights into what’s happening inside our Function. We can do that using the following sentence: Another option, especially if we are developing our Azure Functions inside Visual Studio, is to run the Function locally.

Today I’m going to speak about another important Best practice, Tips, and Tricks that you need to know before you start to develop your Logic App solutions: Choose properly your developer tools.

Today I will talk about naming convention because I think this is so critical to implement from day one, and people tend to forget. We earlier addressed the importance of providing a good naming convention to your Logic App name and actions inside your business process. Today we will speak about the Connectors (or API Connections) naming convention.

Today I’m going to speak about another critical Best practice, Tips, and Tricks that you need to implement while administrating your cloud integration resources: Control your connectors (API connections).

This blog is a quick guide on how we can use BAM with Power Automate.

One of my favorite features in Serverless360 is the monitoring calendar. It is something we added in 2022. The feature aims to help give you a view over time about when your business application has experienced problems that would have triggered warnings or errors based on the monitoring you have configured.

Happy to announce that Serverless360 has extended its support for all Azure resources. In this blog, we will be discussing the March 2022 release of Serverless360.

Happy to announce that Serverless360 has extended its support for all Azure resources. In this blog, we will be discussing the Spring 2022 release of Serverless360.