Function Apps Management
  • 25 Sep 2020
  • 3 Minutes to read
  • Dark
  • PDF

Function Apps Management

  • Dark
  • PDF

Article Summary

Once an Azure Function App is associated with Serverless360 Composite Application, below are the various actions that can be achieved. This reduces switching to the Azure portal.

Start/ Stop/ Restart the Azure Function

Azure Function can be started or stopped from Serverless360 itself. It is also possible to restart the Azure Function app

View Properties

The Properties option in the Function App operation list can facilitate viewing the Azure Function App properties as below

Azure Functions - View Properties

View Function Properties

Every Azure Function App might contain any number of Functions and it is possible in Serverless360 to view their properties that would include the Binding details

Azure Functions - View Functions Properties

Test Function

As we know that Azure Function App might contain any number of Functions, It is now possible to test these functions from serverless360. This is supported for Functions with any type of trigger. For example, to test an Http triggered Function, the user will be allowed to select the request method say GET or POST and add Headers, Query parameters and Message body. After providing the details, a test run can be made and the response along with the status code will be displayed.
test azure function

Access Invocation Logs

A significant capability that Serverless360 offers with respect to Azure Function App management is access to the Invocation Logs of the Functions. One shall get a quick summary of the Function invocations based on the success or failure of the invocation. It is also possible to filter the invocation logs by date to view the invocations on a specific day. If the requirement is to get those invocations those have duration more than a specific value, it is possible to filter the logs based on operators like greater than, greater than or equal to on duration.

Access Invocation Details

Serverelss360 also facilitates viewing the invocation details of every invocation log. In case of the invocation being successful, the invocation detail would contain information on the trigger reason, invocation request details and the output details as below
Azure Functions - Invocation logs

In case of a failed invocation, the invocation details will have information on the exception type, error details and log output with complete error output for further investigation as below

Azure Functions - Invocation logs Details

Monitoring Azure Function for failure is possible using Serverless360 Watch Monitor and for the expected state using Status and Threshold monitors. Check the documentation on Monitoring Azure Functions for more details

Enable/ Disable Functions

Functions within a Function App can be enabled or disabled from Serverless360 itself. Bulk operation is also possible to edit the state of multiple functions at a go.
Azure Functions - EnableDisableFunctions


Operations like Start/ Stop that changes the state of the associated Function App are tracked under Governance and Audit section.

Manage Keys

Security can be implemented in Azure Functions by creating keys at the Function level. If there is a key created for a Function, then the Function expects the key as a header to authorise any Http request. If no key is created, no key is required for the Http requests to get authorised.
Serverless360 now provides capability to manage keys at Function level.

Invoke Triggers

Azure Function supports different type of triggers like Http, Service Bus Queue, Timer, etc. There may be scenarios where an invocation of the Function fails, and the user needs to reinvoke it. There is no possibility to do it apart from posting the message of the failed invocation to the Trigger of the Function (this is not feasible in Timer triggered Function). Serverless360 provides the capability to invoke the Function by sending a message to the Trigger. User can achieve this by providing the Trigger details in Invoke Function screen and by sending the message. For example, if the Function is a Service Bus Queue triggered one, the user can provide the Queue connection details and post the message. Right now, the Triggers supported in Serverless360 are Service Bus Queue, Service Bus Topic, Event Grid and Http.

We'd love to hear your thoughts
Please visit our feedback system to suggest new Features or Enhancements. You can also take a look at our Roadmap

Was this article helpful?