← Return To Home

10 new capabilities in Serverless360

In recent months, we have made remarkable improvements to Serverless360. In terms of expanding the technology scope, Serverless360 has now got capabilities for Web Apps, Web Jobs, and APIM. Product functionalities have also been enhanced -Explorer View in Composite Application dashboard, Topology diagram for a Composite Application, End to End Tracking, improved Automated Activities are few among the recent developments. This blog will introduce the top 10 new capabilities recently added to Serverless360.

  1. Enhanced Composite Applications:
  2. A consulting company manages Serverless solutions of multiple of their customers. The organization needs one platform to manage and monitor all their Serverless applications. The expectations from the monitoring tool would be the following:

    • The Organization hierarchy needs to be depicted in the application to evaluate the impact of an issue
    • The Support team should be well equipped to provide prompt response to their customers

    Serverless360 can be the one platform solution for Azure Serverless monitoring and management.

    • Illustrate organization structure using hierarchical Composite Applications
    • Group multiple Composite Applications into Composite Application Groups which can represent Business Units in your organization
    • Serverless360 can be the one platform solution for Azure Serverless monitoring and management
    • Create a topology diagram that would describe the interaction between the entities. With the status of the entities readily available, diagnose any issue in the business orchestration.
    • Topology diagram that describes the interaction between the entities

    Read more on this feature here.

  1. End to End Tracking
  2. Where did the message go? Is the frequent question the support team finds it hard to find an answer for?

    Consider the Business orchestration below, for every new order received in the Service Bus Queue several parallel processes need to be executed. Each process is defined by a Logic App.

    There is a great possibility of this message failing to pass through a stage. What is required is an end to end tracking solution that can clearly figure out which stage did my business transaction fail and why did it fail?
    End to End Tracking

    Serverless360 now lets you define multiple business processes within every Composite Application. Each business process, in turn, can have multiple stages.

    • Track messages through stages in your Business transaction
    • Identify failures at any stage of the business transaction
    • Get immediate access to the exception details
    • Reprocess the failures to restore the application
    • Search for a message
    • Save searches for quick access

    Read more on this feature here.

    Serverless360 define multiple business processes within every Composite Application

    Serverless360 is one platform to manage and monitor Azure Serverless Applications

  1. Correlate Logic App’s resubmitted runs
  2. In an Ecommerce Application, the Logic App defines the complete workflow. It is important to resubmit the failed runs of this Logic App.

    Though this is possible through the Azure portal, the challenge is that one cannot find any correlation between the parent runs which are resubmitted and child runs which are resubmitted version of the parent runs.

    In real time, it would be required to ignore certain runs from the further investigation.

    Correlate Logic App’s resubmitted runs
    • Resubmit Log App runs from Serverless360 itself
    • Get correlation tags automatically added. The parent runs which are being resubmitted will be assigned with ‘Resubmitted’ tag and that child runs which are resubmission of a parent-run would get a tag ‘Resubmission of
    • It is also possible to drill down to the input and output binding of a trigger and run actions of each Parent and child runs
    • If you want to let your team members know, that certain Logic App Runs need to be ignored from further investigation, that is also achievable by adding ‘Ignored’ tags with reason
    Resubmit Log App runs from Serverless360 itself
  1. Auto clean old Storage blobs:
  2. Consider a Fleet Management System, where client devices send telemetry information to Event Hub. Event Hub captures this data into a Storage blob. Meanwhile, the Event Hub also fires an event to the Event Grid which passes on the event to the On-Premise system, exposed through a Relay. Upon receiving the event, the on-premise system processes the blob data but doesn’t remove.

    There is a necessity for an automated system that can clean up the blob data older than 5 days. Hence saving the unnecessary cost spent on processed data.
    Auto clean old Storage blobs
    • Serverless360 activities is now extended to process on Storage Blobs
    • Create a scheduled activity to auto clean blobs by type which are created/ modified before specified number of days

    Read more on this feature here.

    Serverless360 activities is now extended to process on Storage Blobs
  1. Monitor Web Apps:
  2. Consider a Blog portal, the website of which is hosted in an Azure Web App. Since this website is the Customer facing component of the whole product, it is necessary to monitor the Web App for any errors, its performance, Data Flow and so on.

    5.1_MonitorWebApps
    • Serverless360 Data Monitor can enable monitoring on extensive list of Web App metrics
    • The choice of multiple available metrics will enable monitoring Web App for detecting errors, Data Flow, CPU utilization, performance and so on
    • Monitor state of Web App in a Status or Threshold monitor
    • Auto Correct Web App state to expected state as and when required

    Read more on this feature here.

    Monitor Web Apps
  1. Manage and monitor Web jobs:
  2. The Blob portal orchestration include a good number of Web Jobs to achieve background triggered and continuous actions. Managing and monitoring them is critical to ensure the system works as expected.

    One key challenge in managing their state in the Azure portal is that the state of the web job needs to be modified one by one. What is needed here is a capability to select a multiple of them and modify their state at a go.

    6.1Manage_Monitor_Web_Jobs

    Serverless360 now expands its capabilities to offer management and monitoring for Web Jobs.

    • Overcome the challenge in managing Web Job state using Serverless360
    • Run multiple of Triggered Web Jobs in similar state
    • Start or Stop multiple Continuous Web Jobs in same state
    • Monitor the Web Jobs current state against the expected state in a threshold or status monitor

    Read more on this feature here.

    Serverless360 Data Monitor can enable monitoring on extensive list of Web App metrics
  1. Monitor APIM:
  2. APIM plays a critical role in the orchestration. APIM are typically used to expose web endpoints or Logic App endpoint or Azure Function endpoint.

    Check if the APIM is Online without pinging its endpoint. There are additional requirements to monitor it in multiple levels like product, endpoint and operations at various perspectives too.

    Read more on this feature here.

    Serverless360 now expands its capabilities to offer management and monitoring for Web Jobs
  1. Save entity properties as Template:
  2. Organization wants to define a standard in Entity definition. Any business application is expected to create entities adhering to this standard. Say all Service Bus queues in the organization is expected to have a predefined property set like Requires Duplicate Detection should be enabled, Time to Live should be set to 10 mins, Partition should be enabled and so on. Since achieving this manually would be time-consuming and prone to errors, need an application in place which can facilitate quick create entities adhering to organization standards.

    Save entity properties as Template
    • Serverless360 has now got a new menu added, that would facilitate creating and managing templates which can define the organization standard for entities by type
    • Templates can be created from scratch for Service Bus Queues & Topics, Event Hubs and Relays
    • It is also possible to save property of an entity of the above-mentioned types into a template
    • These templates can be used while creating the entities of similar type

    Read more on this feature here.

    8.2_Save_Template

    Serverless360 is one platform to manage and monitor Azure Serverless Applications

  1. Active message processing Activity:
  2. In the E-commerce Application it is found that certain messages are left behind unprocessed by the Logic App. The requirement here is an automated activity that can pick up the unprocessed messages and move them to another Queue. A Restore system will take care of processing these moved messages. This is expected to happen at regular intervals without any manual intervention.

    Active message processing Activity
    • Serverless360 now has extended its message processing capabilities to active messages in Service Bus Queues and Topics too
    • Create an automated scheduled activity to move those messages left behind unprocessed by the Logic App listening to the Queue
    • Activities can now be scheduled in hourly basis too

    Read more on this feature here.

    9.2_Process_Active_Messages
  1. Auto Correct Entity state:
  2. Consider an e-commerce scenario where the logic app plays a critical role. State of the logic app is expected to be enabled. If the logic app is disabled for any reason the incoming messages in the service bus queue, the logic app is listening to, would pile up. Once the Time To Live value of these messages expire, they move into the dead letter.

    The state of the Logic App will indeed impact the status of other entities in the orchestration. Hence it becomes necessary to continuously monitor the state of the logic app and correct as and when required. Manually achieving this might be tedious and prone to errors.

    The threshold monitors in Serverless360 which were detecting violation in the state of entities is now equipped with the auto correct capability to modify the state of the entity and restore the business application to a healthy state without any manual intervention.

    Auto Correct Entity state
    • Turn on auto correct option in a threshold monitor monitoring state of any of the supported Entity types
    • Set Max retry count to define how many times Serverless360 is expected to try restoring the state to expected state

    Read more on this feature here.

    10.2_AutoCorrect

We would love to know you feedback on ourFeedback Portal.

Author: Ezhilarasi Chezhiyan

Ezhilarasi Chezhiyan, Technical Lead for the product, Serverless360, at Kovai Systems India Pvt Ltd. She has over 8 years of experience in Software development with knowledge spectrum spread across various domains. Problem-solving is her passion and she believes in the quote by Albert Einstein- "Intellectual growth should commence at birth and cease only at death"