Manage Monitoring of Functions in Azure

Unlock secure, remote management and monitoring of Azure Functions with Nodinite. Empower your teams to take action, troubleshoot, and optimize Functions—without direct Azure portal access.

Why choose Nodinite for Azure Functions?

✅ Remotely enable, disable, test, and view history for Functions
✅ Empower support and DevOps teams with self-service and actionable insights
✅ Reduce risk by limiting Azure portal access and centralizing control
✅ Achieve operational excellence with unified monitoring and management

Nodinite provides delegated management and deep visibility into selected Functions. Monitoring Agents alert you instantly to problems and provide direct access to actionable details—no Azure portal required. By reducing access, you minimize attack vectors and lower the risk of disruption to mission-critical services.

For more on secure cloud operations, see Microsoft Learn: Azure Security Best Practices

Diagram: Nodinite connects to Azure Functions and Web Site resources for monitoring and management.

Example: Different types of Azure Function-related Monitoring Resources and Categories in a Nodinite Monitor View.

Management Features

For Resources in Role-based Monitor Views with Remote Actions privileges, you can:

• Remotely Enable, Disable, Test, and View history for Functions
• Edit thresholds and Manage keys
• List and clear failed executions
• Start/Stop Function Apps and manage API keys

As an Administrator with access to Remote Configuration, you can Configure[] the Azure Agent to monitor Functions in Azure.:

Function

The 'Function' Category provides one Resource for each Azure Function found, using its name as the Resource name.

Example: List of Azure Functions in a Nodinite Monitor View.

See Monitoring Functions: The Functions category provides Resources that display the evaluated monitored state according to built-in rules.

The following Remote Actions are available for the Functions Category:

• Enable
• Disable
• View history
• Details
• Edit
• Manage Keys
• Test

Example: Available Remote Actions for each Function Resource.

Enable Function

You can Enable a disabled Azure Function by clicking the Action button and then clicking on the Enable menu item within the 'Control Center' section.

Enable Function Remote Action.

A prompt will then verify your intent to Enable the selected Function.

Confirm intent to Enable the selected Azure Function.

Next, the result from the operation is presented. This can be either success or failure.

Here's an example of a successful result enabling a disabled Azure Function.

Disable Function

You can Disable an enabled Azure Function by clicking the Action button and then clicking on the Disable menu item within the 'Control Center' section.

Disable Function Remote Action.

A prompt will then verify your intent to Disable the selected Function.

Confirm intent to Disable the selected Azure Function.

Next, the result from the operation is presented. This can be either success or failure.

Here's an example of a successful result disabling an enabled Azure Function.

View history

To view the history for the Function Resource; Click the Action button and then click on the View history menu item within the 'Control Center' section.

Use the 'View history' action menu item to open the modal for the selected Function.

Next, click the option to present the modal.

Example of viewing the history modal for a specific Azure Function.

You can change the lookback period, click the Sync button to perform the search.

Click on the small button on each row to present all logged events from within a Run.

Example of viewing detailed events from a specific run of the Azure Function.

Functions Details

To view essential Details about the selected Function Resource; Click the Action button and then click on the 'Details' menu item within the 'Control Center' section.

Example of viewing the history modal for a specific Azure Function.

Next, click the option to present the modal.

Example of viewing detailed information about a specific Azure Function.

Edit Function

💡Manage Monitoring Thresholds

To edit and manage the Function Resource; Click the Action button and then click on the Edit menu item within the 'Control Center' section.

Example of the Edit modal for a specific Azure Function.

Next, click the option to present the modal.

Example of the Edit modal for a specific Azure Function.

You can manage the following fields:

• Description - A user-friendly description about the Azure Function.
• Last clear date time - Ignore execution errors before this point in time (NOTE: Time is UTC).
• Use global thresholds - When checked, the monitoring thresholds uses the global settings
• Lookback period - How far back in time to look for problems. The monitoring evaluation uses this value if the current time is higher than the last clear date-time + the lookback period
• Min execution count (Warning) - The least number of invocations within the lookback period, otherwise, raise a Warning.
• Min execution count (Error) - The least number of invocations within the lookback period, otherwise, raise an Error.

  Enter the monitoring thresholds for the count-based evaluation. -1 means that the check is disabled (default)

• Max execution count (Warning)
• Max execution count (Error)
• Duration (ms)
  • Warning
  • Error

Click the Save button to persist changes. The Agent is using caching; allow a few minutes to get synchronized with the new values.

Manage Keys

You can view and manage the keys in use to authenticate with invocations to the Azure Function. Click the Action button and then click on the Manage Keys menu item within the 'Control Center' section.

Example of managing API keys for a specific Azure Function.

Next, click the menu item to present the modal.

Example of the Manage Keys modal for a specific Azure Function.

You can create new keys, renew existing keys, and delete keys no longer in use. Click the New Function Key button to create a new Function Key.

Example of the button used to create a new Function Key.

A panel appears and here is where you add the mandatory name and the optional key value. Leave the field empty to allow the system to create it for you.

Example of the properties required to create a new Function Key.

Click the ✅ button to create a new key. You must confirm the intent.
Example of confirming intent to create a new Function Key.

On each Key in the table, there is an 'Action' button with the following Remote Actions:

• Renew
• Delete

Example of the available actions for each Function Key.

Renew Function Key

Click the Renew menu item in the Actions button for an existing Key to generate a new value.

Example of the Renew action for a specific Function Key.

You must confirm the intent.

Example of confirming intent to renew a Function Key.

This operation may take a few seconds. The Modal reloads once the operation has finished.

Delete Function Key

You can delete an existing Key. Click the Delete menu item in the Actions button for an existing Key to generate a new value.

Example of the Delete action for a specific Function Key.

You must confirm that you want to delete the selected Key.

Example of confirming intent to delete a Function Key.

This operation may take a few seconds. The Modal reloads once the operation has finished.

Test Function

Experience fast, secure testing of your Azure Functions directly from Nodinite. Empower your teams to validate deployments, troubleshoot issues, and confirm integration points—without needing direct Azure portal access.

✅ Why test Functions remotely?

• Accelerate troubleshooting and root cause analysis
• Enable secure, self-service validation for support and DevOps teams
• Confirm integrations work as expected before and after changes
• Reduce risk by limiting Azure portal access

How to test an Azure Function with Nodinite:

1. Click the Action button for your selected Function Resource, then choose Test from the 'Control Center' menu.
   
   Example of using the 'Test' action menu item to open the modal for the selected Functions.

2. The modal appears, allowing you to interact with the Function.
   
   Example of the Test modal for a specific Azure Function.

3. If the Function uses an HTTP trigger, you can send requests directly from the modal. If not, Nodinite clearly indicates that testing is not available for the selected Function.
   
   Example of the Test modal indicating that testing is not implemented for the selected Azure Function.

4. The modal provides three tabs for customizing your test request:

• Body – Enter the payload for POST/PUT requests
• Params – Add query string parameters
• Headers – Specify custom HTTP headers

5. Choose the correct HTTP VERB (such as POST or GET) and provide any required authentication keys.

6. Click the 'Run' button to execute your test. Nodinite instantly displays the response, helping you validate the Function’s behavior and troubleshoot issues.

Function - Failed Executions

Take control of error management and root cause analysis for your Azure Functions with Nodinite's Failed Executions feature. Instantly surface problems, accelerate troubleshooting, and empower your teams to resolve issues before they impact business operations.

Why monitor failed executions?

• Proactively detect and resolve errors in mission-critical Functions
• Reduce downtime and improve service reliability
• Enable support and DevOps teams to act fast—no Azure portal access required
• Centralize error management for compliance and audit needs
• Use lookback periods to focus on recent, actionable errors and filter out historical noise

The 'Function - Failed Executions' Category creates a Resource for each Azure Function with failed runs.

Example: Monitor View showing a list of 'Function - Failed Executions' Resources.

See Monitoring Functions for more details about error monitoring and best practices.

The Functions - Failed Executions category displays the monitored state based on built-in rules (errors detected in the lookback period). The lookback period determines which failed executions are shown, helping you focus on the most relevant and recent issues. Adjusting the lookback period allows you to filter out older errors and concentrate on current operational health.

Available Remote Actions:

• List failed executions
• Clear failed executions

Example: Available Remote Actions for each 'Function - Failed Executions' Resource.

List failed executions

💡Quickly view all failed executions for any Function Resource:

1. Click the Action button and select List failed executions from the 'Control Center' menu.
   
   Use the 'List failed executions' action menu item to open the details modal for the selected Azure Function.
2. The modal appears, showing all failed runs within the selected lookback period.
   
   Example: Modal listing failed executions for a Function.
3. You can also Clear all Failed Executions directly from this modal—this feature is also available on the Resource in the Monitor View.
   
   Example of the button used to clear all failed executions for the selected Azure Function.
4. If the Clear Date Time is set and within the lookback period, the table is filtered. Click Sync to reload content for the selected lookback period and ensure you are seeing the most up-to-date error information.
   
   Example of a limited result set due to the configured Clear Date Time.

Clear failed executions

💡Reset error state and focus on new issues:

1. Click the Action button and select Clear failed executions from the 'Control Center' menu.
   
   Example of using the 'Clear failed executions' action menu item to clear previously failed executions.
2. Confirm your intent to proceed.
   
   Example of confirming intent to clear previously failed executions.
3. If successful, a confirmation message appears.
   
   Example of a successful clear operation for failed executions.

For more on error handling strategies and lookback period configuration, see Microsoft Learn: Azure Functions Error Handling

Web Site - Function App

All Azure Functions are hosted on a Web Site (Function App). The Nodinite Azure Monitoring agent creates one Resource for each Web Site. The Category is Web Site - Function App
Example: List of 'Web Site - Function App' Resources in a Nodinite Monitor View.

The following Remote Actions are available for the Web Site - Function App Category:

• Details
• Manage API Key
• Start
• Stop

Example: Available Remote Actions for each 'Web Site - Function App' Resource.

Function App Web Site Details

To view essential Details about the selected Web Site - Function App Resource; Click the Action button and then click on the Details menu item within the 'Control Center' section.

Example of details action menu item to open the details modal for the selected Web Site with Azure Functions.

Next, click the option to present the modal.

Example of viewing detailed information about a specific Azure Function App Web Site.

Tip

The Statistics section helps gain insights about the frequency and duration of Runs. You can use this data to configure the Non-Events type of feature. You can review the following properties (sorted and grouped by Azure Function):

• Most succeeded
• Most error-prone
• Fastest
• Slowest
• Average execution-time
• Last Run
• Newest Run
• Potentially dead - N/A There is no data to present within the lookback period.

Edit (Application Insights)

You can manage the description of the Application Insights Resource associated with the selected Web Site - Function App Resource; Click the Action button and then click on the Edit menu item within the 'Control Center' section.

This feature is documented in detail in the Azure Agent - Managing Application Insights - Manage API Key section.

Start

You can Start a stopped Azure Function Web Site, click the Action button and then click on the Start menu item within the 'Control Center' section.

Start Function Web Site Remote Action.

A prompt will then verify your intent to Start the selected Web Site.

Confirm intent to Start the selected Azure Function Web Site.

Next, the result from the operation is presented. This can be either success or failure.

Here's an example of a successful result starting an Azure Function Web Site.

Stop

You can Stop a started Azure Function Web Site, click the Action button and then click on the Stop menu item within the 'Control Center' section.

Stop Function Web Site Remote Action.

A prompt will then verify your intent to Stop the selected Web Site.

Confirm intent to Stop the selected Azure Function Web Site.

Next, the result from the operation is presented. This can be either success or failure.

Here's an example of a successful result stopping an Azure Function Web Site.

Next Step

Monitoring Functions
Configuring the Nodinite Azure Monitoring agent

Related Topics

Azure Logging and Monitoring Overview
Prerequisites for Azure Agent