Operations | Monitoring | ITSM | DevOps | Cloud

2022 was all about Azure enthusiasts, to whom we constantly strive to deliver breakthrough features for Azure management and impart knowledge with valuable content in collaboration with industry experts. Now, we are glad to bring you all our achievements of the past year.

We have recently added the API Monitoring feature to Serverless360 and this opens up a wide range of monitoring opportunities. The principle of API Monitor is that you have an API endpoint that you want Serverless360 to periodically call and then you will make assertions against the response to check if the API is healthy or not.

In a previous article, I discussed how you could use API Management as a proxy for the Serverless360 BAM API. In the real world, I have used this approach a few times because I prefer it to the custom connectors that you can use with Logic Apps which are sometimes painful to use from a DevOps perspective and have known performance limitations that can affect the latency and throughput for connections Logic Apps make to Cloud Services.

Enterprise use of Microsoft’s Azure Cloud Services is expanding at an unprecedented rate as cloud computing usage expands. However, enterprises that have recently switched to Azure continue to have serious concerns about Azure cost efficiency. Managing the costs associated with Azure cloud infrastructure differs from reducing the cost of an on-premises server because Azure cloud infrastructure can be built as needed, typically outside the control of a traditional IT department.

In the software industry, monitoring and observability come hand in hand and are referenced simultaneously, but both are not the same thing. Having the right tools for these capabilities is vital to keep your systems, data, and security perimeter safe. With cloud solutions topping up in the integration space, great tools have been available in the market, and choosing the right one would be challenging.

Today I’m going to speak about another important Best practice, Tips and Tricks that you need to take into consideration while you are designing and maintaining your business processes (Logic Apps): Protect your Logic Apps.

The critical use case for BAM is to provide a simplified business-friendly view of the integrated processes that are key to your business. In business today, Robotic Process Automation (RPA) is a trending technology. While it has been around for quite a long time, it has gained a significant boost in popularity alongside the popularity of citizen developer and maker use cases.

Today I’m going to speak about another important Best practice, Tips and Tricks that you need to take into consideration while you are designing your business processes (Logic Apps): Foreach Parallelism.

In the fast-growing Azure space, it is essential to scale your business as Azure scales up. Azure is cost efficient by providing a pay-as-you-go model, but it is still necessary for enterprise users to undergo a Cost Analysis to keep their budget at stack. Let us consider a scenario, you’re a manager in your organization, and your team has been using Azure for the last several months. It has created multiple resources that cost money.

From our experience handling Azure Service Bus messages, one frequent suggestion we get from the support person is to download messages from Azure Service Bus entities like Queues and Topic Subscriptions. By downloading the messages as a local copy, it becomes easy for them to debug the messages and use it at a later point in time. Basic knowledge of Azure Service Bus messaging entities is a pre-requisite for the better understanding of this feature.