April 2020
  • 03 Apr 2020
  • 4 Minutes To Read
  • Contributors
  • Print
  • Share
  • Dark
    Light

April 2020

  • Print
  • Share
  • Dark
    Light

April 03, 2020

This release brings in the following capabilities:

  • Manage Keys for Azure Function
  • Invoke Azure Function
  • Test Azure Function
  • Action Needed List for Logic App
  • Invoke Logic App Trigger
  • Retry Chain for Logic App Run
  • Favorite Run List for Logic App
  • OAuth in API Monitoring
  • Data Monitor Improvements

Manage Keys for Azure Function

Serverless360 enables users to manage the Azure Function 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. Serverless360 now provides capability to manage keys at Function level.

ManageKeys

For more information about this feature, check here.

Invoke Azure Function

There may be scenarios where an invocation of the Function fails, and the user need 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.

InvokeFunction

For more information about this feature, check here.

Test Azure Function

Serverless360 now enables users to test the Azure Functions. A message can be posted to a Function and the result of request will be displayed along with the status code.

test azure function

For more information about this feature, check here.

Action Needed List for Logic App

There may be multiple times that your Logic App may experience error conditions that you need to manage. Serverless360 provides the capability to easily identify the runs that requires user attention by grouping it in the 'Action Required' tab present in the Logic App.

A detailed working of the above capability is shown below.
ActionRequiredRuns.gif

For more information about this feature, check here.

Invoke Logic App Trigger

When managing Logic Apps , if there are any errors then Azure Portal is used to resubmit a Logic App instance which will cause it to rerun. While this is useful there are some limitations with it. In particular if the input message which triggered the Logic App was incorrect and caused the error in the Logic App then with the Azure Portal as an operator I am not able to modify the message to correct the root cause of the problem and kick off the Logic App with a modified message.

Invoke Logic App Trigger feature will allow the users to modify a message and resubmit it to an endpoint which can allow Logic App to be recovered from the error condition.

A detailed working of the above capability is shown below.
ResubmitRun.gif

For more information about this feature, check here.

Retry chain for Logic App Run

When working with Logic Apps and there can scenarios where the Logic App instance has been retried a number of times and it is continuing to get an error, leaving user in a position where it is difficult to troubleshoot the issue. It is also difficult to workout which Logic App instances are retries of which. Serverless360 provides the capability to easily visualize the retries for a specific Logic App run.

A detailed working of the above capability is shown below.
RetryChain.gif

For more information about this feature, check here.

Favorite Run List for Logic App

When managing Logic App there may be a need to investigate a specific Logic App run . This may take some time to do. While investigating, other Logic App instances will be running and it makes it hard to find the original Logic App instance. Serverless360 provides the capability to mark a Logic App run as favorite to easily find a particular run and access it. This favorite list will be specific the user.

A detailed working of the above capability is shown below.
FavoriteRuns.gif

For more information about this feature, check here.

OAuth in API Monitoring

Serverless360 API monitoring helps to set up monitoring on the endpoints and get to know if the API is healthy. If there is a state mismatch, you will be notified of the error details so that you can immediately take action on the API. As an enhancement to API monitoring, OAuth authentication mechanism is built. In OAuth authentication, the authentication token is obtained from the user-provided Endpoint.

OAuth-1

For more information about this feature, check here.

Data Monitoring Improvements

  • Serverless360 now allows the users to configure a metric value against another metric value as warning and error threshold in Data Monitor. For example, In a Logic App, the number of runs started can be directly compared with the number of succeeded runs.

MetricComparsion.png

  • Data monitor will usually send alert to the configured notification channel if any of the configured metric violates the warning or error threshold, now an option is available to send alert only if all the configured metrics violates the warning or error threshold.

AndDatamonitor.png

For more information about this feature, check here.

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?