Bring Your Own Backend (BYOB) is a deployment model for Serverless360 Business Activity Monitoring, where the backend of Business Activity monitoring environment (i.e.) the resources responsible for tracking, processing, and storing the user's data, will be deployed in the user's Azure Subscription. This deployment model is preferred for users who need to track a large amount of data.
Bring Your Own Backend
Configure your own backend for Business Activity Monitoring (BAM) environment by choosing User your Azure subscription deployment model during the Getting started process.
The first step in implementing BYOB in your Business Activity Monitoring (BAM) environment is to provide and validate Service Principal information. Click the Next button once the validation is successful.
The second step is to choose a Resource group and a region from the available dropdown menu.
The third step is to customize the servicing and pricing tier for SQL Database, Processor Function App, Tracker Function App, and Service Bus Namespace. You can also tick the Reuse app service plan checkbox to apply the same Plan type as the Processor Function App for Tracker Function App.
You can also make use of the Azure calculator hyperlink to estimate the cost of Azure products based on your pricing tier customization.
Once all the required information has been entered, click the Initiate deployment button to complete the setup.
You will be provided with a video that briefs about how Business Activity Monitoring works with a simple use case. The resources will be deployed in a few minutes, along with a sample configuration explained in the video.
Managing Service principal
- The Service principal credentials provided during the time of deployment can be updated at any point in time. It is available in the Actions dropdown on the Serverless360 Business Activity Monitoring (BAM) Homepage.
Accessing SQL database password
- An Azure SQL database will be deployed as a part of the Bring Your Own Backend (BYOB) deployment and a system user and password will be created for it. The connection string with the user and password details can be fetched from the BAM Storage details section as shown below:
All the transactions occurring in BAM will be logged in the application insights configured along with the deployed function apps. By default, logs of type Information and Exception will be logged for both the function app's functions. If the transactions are huge, the default configuration in the function app settings can be overridden, reducing the cost incurred by app insight. Limiting log type to "Error" is a recommended setting.
The following settings can be added to the deployed API function app:
The following settings can be added to the deployed Processor function app: