Manage Monitoring of Functions in Azure

Manage Azure Functions securely and remotely with Nodinite. Your teams act on, troubleshoot, and tune Functions without direct Azure Portal access.

What you achieve with Nodinite:

• ✅ Remotely enable, disable, test, and view history for Azure Functions
• ✅ Self-service and actionable insights for support and DevOps teams
• ✅ Less risk, because fewer people need Azure Portal access
• ✅ Unified monitoring and management in one place

Nodinite delegates management of selected Functions to the people who need it. The Azure Monitoring Agent, one of the Nodinite Monitoring Agents, alerts you through Alarm Plugins when a Function breaks, and gives direct access to the details. Less access means fewer attack vectors and less risk of disrupting mission-critical services.

Want to understand the monitoring model first? Start with Monitoring Functions to see how the agent discovers and evaluates Azure Functions and shows them in Monitor Views. For more on secure cloud operations, see Microsoft Learn: Azure Security Best Practices.

Diagram: The Azure Monitoring Agent (blue) reads Function Apps and Functions in Azure (purple) and hands their state and Remote Actions to the Monitoring Service and Monitor Views (green).

Example: 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, your Users run these actions from the Web Client, grouped by Category:

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. The Resources show the monitored state that Nodinite evaluates according to built-in rules; see Monitoring Functions.

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

The Function Category has the Remote Actions listed in the Management Features table and described below.

Example: Available Remote Actions for each Function Resource.

Enable Function

To Enable a disabled Azure Function, click the Action button and then the Enable menu item in the 'Control Center' section.

Enable Function Remote Action.

A prompt asks you to confirm that you want to Enable the selected Function.

Confirm intent to Enable the selected Azure Function.

Nodinite then shows the result of the operation, either success or failure.

Example of a successful result enabling a disabled Azure Function.

Disable Function

To Disable an enabled Azure Function, click the Action button and then the Disable menu item in the 'Control Center' section.

Disable Function Remote Action.

A prompt asks you to confirm that you want to Disable the selected Function.

Confirm intent to Disable the selected Azure Function.

Nodinite then shows the result of the operation, either success or failure.

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 the View history menu item in the 'Control Center' section.

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

The modal opens.

Example of the history modal for a specific Azure Function.

Change the lookback period and click the Sync button to search again. Click the small button on a row to show all logged events from that Run.

Example of 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 the Details menu item in the 'Control Center' section.

The 'Details' action menu item for the selected Azure Function.

The modal opens.

Example of detailed information about a specific Azure Function.

Edit Function

Tip

Use Edit to manage the monitoring thresholds, including the Non-Events Monitoring style checks (too few, too many, too lengthy).

To edit the Function Resource, click the Action button and then the Edit menu item in the 'Control Center' section.

The 'Edit' action menu item for the selected Azure Function.

The modal opens.

Example of the Edit modal for a specific Azure Function.

You can manage the following fields:

• Description - A user-friendly description of 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 use the global settings from the Configuration.
• Lookback period - How far back in time to look for problems. The evaluation uses this value if the current time is later than the last clear date time plus the lookback period.
• ⚠️ Min execution count (Warning) - The least number of invocations within the lookback period; fewer raises a Warning.
• ❌ Min execution count (Error) - The least number of invocations within the lookback period; fewer raises an Error.

  Enter the monitoring thresholds for the count-based evaluation. -1 disables the check (default).

• ⚠️ Max execution count (Warning)
• ❌ Max execution count (Error)
• Duration (ms)
  • ⚠️ Warning
  • ❌ Error

Click the Save button to persist changes. The agent caches settings; allow a few minutes for the new values to take effect.

Manage Keys

View and manage the keys that authenticate invocations of the Azure Function. Click the Action button and then the Manage Keys menu item in the 'Control Center' section.

The 'Manage Keys' action menu item for the selected Azure Function.

The modal opens.

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

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.

In the panel, enter the mandatory name and, optionally, the key value. Leave the value empty to let the system generate it.

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

Click the ✅ button to create the key, and confirm your intent.

Example of confirming intent to create a new Function Key.

Each Key in the table has an 'Action' button with these Remote Actions: Renew and Delete.

Example of the available actions for each Function Key.

Renew Function Key

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

Example of the Renew action for a specific Function Key.

Confirm your intent.

Example of confirming intent to renew a Function Key.

The operation may take a few seconds; the modal reloads when it finishes.

Delete Function Key

Click the Delete menu item in the Actions button of an existing Key to delete it.

Example of the Delete action for a specific Function Key.

Confirm that you want to delete the selected Key.

Example of confirming intent to delete a Function Key.

The operation may take a few seconds; the modal reloads when it finishes.

Test Function

Test your Azure Functions directly from Nodinite to validate deployments, troubleshoot issues, and confirm integration points, without Azure Portal access. Remote testing helps you:

• ✅ Speed up troubleshooting and root cause analysis
• ✅ Give support and DevOps teams secure, self-service validation
• ✅ Confirm integrations work before and after changes

To test an Azure Function from Nodinite:

1. Click the Action button for the selected Function Resource, then choose Test in the 'Control Center' menu.
   
   Example of the 'Test' action menu item that opens the modal for the selected Function.
2. The modal opens, and you can interact with the Function.
   
   Example of the Test modal for a specific Azure Function.
3. If the Function uses an HTTP trigger, send requests directly from the modal. If not, Nodinite shows that testing isn't available for the selected Function.
   
   Example of the Test modal indicating that testing isn't available for the selected Azure Function.
4. Use the three tabs to customize the test request:
   • Body – the payload for POST/PUT requests
   • Params – query string parameters
   • Headers – 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. Nodinite displays the response, so you can validate the Function's behavior.

Function - Failed Executions

Surface Function errors as soon as they happen and resolve them before they affect the business. Monitoring failed executions helps you:

• ✅ Detect and resolve errors in mission-critical Functions, with no Azure Portal access
• ✅ Centralize error management for compliance and audit needs
• ✅ Focus on recent, actionable errors with the lookback period

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.

The state reflects errors detected within the lookback period, so adjust the lookback period to filter out older errors; see Monitoring Functions. The Remote Actions are List failed executions and Clear failed executions.

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

List failed executions

Tip

Quickly view all failed executions for any Function Resource.

1. Click the Action button and select List failed executions in 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 shows all failed runs within the selected lookback period.
   
   Example: Modal listing failed executions for a Function.
3. You can also Clear all Failed Executions from this modal, as well as from 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.
   
   Example of a limited result set due to the configured Clear Date Time.

Clear failed executions

Tip

Reset the error state and focus on new issues.

1. Click the Action button and select Clear failed executions in the 'Control Center' menu.
   
   Example of the 'Clear failed executions' action menu item that clears previously failed executions.
2. Confirm your intent.
   
   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 error handling strategies, 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, in the Web Site - Function App Category. Web Apps without Functions are covered in Managing Web Site.

Example: List of 'Web Site - Function App' Resources in a Nodinite Monitor View.

The Remote Actions are Details, Start, and Stop.

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

Note

Legacy authentication method: Earlier versions of Nodinite used API keys to read Application Insights data for Functions Monitoring. Nodinite now uses an Azure App Registration with Delegated permissions (Application Insights API - Data.Read) for secure, centralized authentication, and API key management is removed. See Prerequisites - Functions and Monitoring Application Insights.

Function App Web Site Details

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

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

The modal opens.

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

Tip

The Statistics section shows the frequency and duration of Runs. Use this data to set the Non-Events thresholds. 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.

Start

To Start a stopped Azure Function Web Site, click the Action button and then the Start menu item in the 'Control Center' section.

Start Function Web Site Remote Action.

A prompt asks you to confirm that you want to Start the selected Web Site.

Confirm intent to Start the selected Azure Function Web Site.

Nodinite then shows the result of the operation, either success or failure.

Example of a successful result starting an Azure Function Web Site.

Stop

To Stop a started Azure Function Web Site, click the Action button and then the Stop menu item in the 'Control Center' section.

Stop Function Web Site Remote Action.

A prompt asks you to confirm that you want to Stop the selected Web Site.

Confirm intent to Stop the selected Azure Function Web Site.

Nodinite then shows the result of the operation, either success or failure.

Example of a successful result stopping an Azure Function Web Site.

Next Steps

• Monitoring Functions
• Configure the Nodinite Azure Monitoring Agent
• Add or manage Monitor View - Grant teams Remote Actions on Functions

Related Topics

• Azure Monitoring Agent Overview
• Azure Logging and Monitoring Overview
• Prerequisites for Azure Agent - Firewall and Functions Monitoring requirements
• Managing Web Site and Monitoring Web Site
• Monitoring Application Insights
• Managing Web Jobs
• Troubleshooting
• Reduce Azure Functions Logging Costs - Lower the Azure cost of logging Azure Functions with Serilog
• Azure Costs for Blob Storage and Event Hub
• Reduce Azure Logic Apps Run History Retention to Lower TCO - see also Azure Logic Apps
• Reduce Azure API Management Logging Costs