Serverless360 – BAM and Resource Map

Serverless360 – BAM and Resource Map

This blog will give you an overview of the session “Serverless360 – Update” presented by Michael Stephenson, Microsoft Azure MVP and Advisor to Serverless360 at Integrate 2020.

This blog covers detailed view of Business Activity Monitoring and Resource Map in Serverless360.


Serverless360 is one platform which provides managing and monitoring of all Azure serverless services. It provides better operational capabilities like message processing, end to end tracking, application visibility and much more.


Microsoft provides us various offerings like Subscriptions, Resource groups and management groups which consists of different Azure resources in it. There are some physical constraints during the deployment of resources, like visibility of the transferring of resources.


Resource Map

The main objective of Resource Map is, to provide logical view for the cloud resources and help in managing those resources actively whenever it changes. Resource Map is a platform to govern Azure resources from different subscriptions at one place.

Resource Map

Key Components

To categorize the resources in terms of,

  • Scopes
  • Logical Resources
  • Environments


Scope states where your resources belong to. Scopes are represented in a tree like structure in Serverless360. Scopes are logical grouping which in turn can have multiple environments and resources underlying. All these can be grouped to represent an organisational hierarchy.


Each resource is logically grouped to its corresponding environment, so it becomes easier to categorize which resources belongs to which environment

Logical Resources

Resource Map indicates that the physical resources are different instances of the same logical resource. Consider you have dev/test/production environments and you could find multiple resources are same, but they are versions of each other.



Mike demonstrated the capabilities of Resource Map. Initially he displayed the Azure portal under which he has got bunch of Resource Groups like production, test, dev. Under the production he has Logic Apps, CDN, an App Service Plan, Event Grid, etc.,


The below picture shows the Scopes section under the Resource Map in Serverless360 portal. The scopes here are represented in tree structure. In this demo, he mainly focuses on “FitApp” scope under the Apps scope.


Next go to the Resources section, where you can synchronize the resources. This synchronizes the Azure resources from different subscriptions under a single scope. The below picture is the result of synchronizing the resources


Applying rules helps in auto allocate resources to scopes, logical resources and environments. Once rules are applied, resources automatically move to the tree.


The nodes are represented green in colour once rules are assigned to them. Click on Resource Assignments and in the grid, you could see list of Logical Resources mapped to an environment. This picture provides the view of resources mapped to an environment.


The below picture represents the comparison of the properties of physical resources in one blade and this is well organized.


Resource Map can detect if any of the resources are not mapped, they will be listed under the unmapped section. And if the mapped resources are not assigned, the nodes will be represented red in colour in the tree structure.

Cost Analysis

Understanding the cost spent on Azure Services is critical, especially while opting for Serverless architecture. Cost visualisation capability in Resource Map feature of Serverless360 comes into provide the required clarity on the spending in your Azure subscription in fact across subscriptions.

The below picture represents the cost of the Application for the Scope – “FitApp”. We could acquire the cost analysis of the resources, types and environments in Pie chart, Line graph and in table view.

Cost Analysis

Business Activity Monitoring

Business Activity Monitoring (BAM) is a way to provide a simplified business focused view on what might be a complex underlying system or group of system interactions that execute to fulfil the business transaction. It facilitates end to end tracking on your business transactions.



This is designed in such a way that the Support operator can spare more time in managing the business solutions.


Here the SAP sends message to the Logic App say IDoc Receiver and the IDoc Receiver sends messages to the different Logic Apps that processes the messages which are in different systems. There are three interfaces and the challenge here is, whether IDoc’s gets published properly or it is synced properly or not.


In Serverless360, there is a BAM connector and there is a BAM Check Point in the Logic Apps to give the view of the things happening.

BAM Demo

In this demo he has a Logic App say IDoc Receiver, he starts the transaction and passes the IDoc messages.

BAM Demo-1

Likewise, there is a Logic App for Consumer. The below picture shows the Logic App for IDoc Consumer.

BAM Demo-2

In Serverless360, under the Business Process you could define a Business process and here there are three transactions one for Publishers and the other two for Consumer. The below picture shows the process diagram for the Consumer1

BAM Demo-3

There are few properties for Receiver IDoc and one among them is LogicAppId which is passed as a header. Property XPath extracts the IDoc number and IDoc type from the XML message that comes from the Logic App connector.

BAM Demo-4

When adding BAM to the Composite Applications, you could view the transactions for every 10 minutes in the Dashboard. You could also see the Logic Apps registered under the Manage Resource section. You can view the architecture under the Service Map.

BAM Demo-5

Click on SAP IDoc number to track the flow of the messages. The below picture shows the message flow for the Consumer2 Logic App and it is executed successfully.

BAM Demo-6

You can filter based on the SAP IDoc number and you could notice that the transaction has been failed for the Consumer1. Click on Reprocess to reprocess the failed message. That’s how you can keep track of messages in Sereverless360 with the help of BAM.

BAM Demo-7

Wrap Up

Hope this blog helps you understand about the latest updates regarding Resource map and BAM. As discussed, Resource Map helps us to efficiently organize and manage the cloud resources under a single scope. BAM provides us the end to end view of the transactions in complex integrations. Extending our regards to Mike for such a lively and interactive session.

Stay connected for further updates regarding Serverless360.

The post Serverless360 – BAM and Resource Map appeared first on Serverless360.

Close Menu