- 3 minutes to read

Monitoring Functions in Azure

Gain full control and visibility over your Azure Functions with Nodinite. This page explains how you can leverage Nodinite to monitor, analyze, and manage your Azure Functions—without relying on the Azure portal.

✅ Instantly detect failed executions and abnormal patterns
✅ Receive real-time alerts for too frequent, too few, or lengthy executions
✅ Effortlessly manage Functions and thresholds remotely
✅ Organize monitoring with category-based views for clarity

Nodinite empowers you to monitor Azure Functions from one or more role-based Monitor Views. You can set custom thresholds, receive actionable alerts, and use remote commands to resolve issues quickly. For details on available Remote Actions, see the Managing Function page.

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

Monitoring Features

State Evaluation – Nodinite evaluates the state of each Function based on your defined policies.

If Nodinite can't check the state of your Functions, chances are no one else can use them either.
Automatic Discovery – The Nodinite Azure Agent uses the Azure Rest API to automatically discover Function Apps and Functions.
Category-Based Monitoring – Group Resources by the Nodinite concept of Categories.
Role-Based Access – Share access to individual items using one or more Monitor Views.

State Evaluation for Functions

Nodinite presents each monitored Function as a Resource. For example, three Functions appear as three separate Resources in Nodinite.

The Resource name matches the deployed Function name.
Monitored Functions belong to the 'Function' Category.

Many other Azure-related Categories exist—see the Azure Logging and Monitoring Overview.
The Application name follows this pattern: Configuration name/Resource Group Name

Each Resource evaluates to a state (OK, Warning, Error, Unavailable). You can override the evaluation by configuring the Expected State for any Nodinite Resource.

Function

For Function Resources, the state evaluates as described below:

State	Status	Description	Actions
Unavailable	Resource not available	Evaluation of the 'Function' is not possible due to network or security issues	Review prerequisites
Error	Error threshold breached	✅ Non-Events Too few Too many Too lengthy ✅ State (Disabled)	Enable
Warning	Warning threshold breached	✅ Non-Events Too few Too many Too lengthy
OK	Within user-defined thresholds	✅ State (Enabled)	Disable View history Details Edit Manage Keys Test

Function Failed Executions

Nodinite evaluates the state of Function - Failed Executions Resources as follows:

State	Status	Description	Actions
Unavailable	Resource not available	Network or security issues prevent evaluation of 'Function - Failed Executions'	Review prerequisites
Error	Errors exist	At least one failed execution occurred within the lookback period	List failed executions Clear all failed executions
OK	No failed executions	No failed executions occurred within the lookback period

Function App Web Site

For Web Site - Function App Resources, the state evaluates as follows:

State	Status	Description	Actions
Unavailable	Resource not available	Evaluation of the 'Function - Failed Executions' is not possible due to network or security issues	Review prerequisites
Error	Errors exist	Function App (Website) is in the Stopped state	Start
OK	No problems exist	Function App (Website) is operational	Details Manage API Key Stop

Alert History for Function

Nodinite makes it easy to analyze the frequency and patterns of Function issues. If your Monitor View allows, you can search for historical state changes for all or individual Functions over a selected period. See 'Add or manage Monitor View' for more details.