Monitoring Functions in Azure
Gain full control and visibility over your Azure Functions with Nodinite. This page explains how Nodinite monitors, analyzes, and helps you manage your Azure Functions, without the Azure Portal.
- ✅ Instantly detect failed executions and abnormal patterns
- ✅ Receive real-time alerts for too frequent, too few, or too lengthy executions
- ✅ Manage Functions and thresholds remotely
- ✅ Organize monitoring with category-based views for clarity
The Azure Monitoring Agent monitors these Categories:
Nodinite lets you monitor Azure Functions from one or more role-based Monitor Views. You set custom thresholds, receive alerts through Alarm Plugins, and use Remote Actions to resolve issues quickly. For details on the available Remote Actions, see Managing Function.

Example: List of monitored Functions in a Nodinite Monitor View.
Function Apps"] -->|"Azure REST API"| AG["fa:fa-monitor-waveform Azure Monitoring Agent"] AG --> OK["fa:fa-check OK
Enabled, within thresholds"] AG --> WA["fa:fa-triangle-exclamation Warning
Warning threshold breached"] AG --> ER["fa:fa-xmark Error
Disabled, failed runs, stopped app"] AG --> UN["fa:fa-ban Unavailable
Not found or no access"] WA --> AP["fa:fa-bell Alarm Plugins"] ER --> AP ER --> RA["fa:fa-bolt Remote Actions"] style OK fill:#93d16d style WA fill:#FFD525 style ER fill:#c33d34,color:#fff style UN fill:#c33d34,color:#fff style AG fill:#2678BD,color:#fff
Diagram: The agent evaluates each Function, failed-execution, and Function App Resource into OK (green), Warning (yellow), or Error and Unavailable (red); Warning and Error raise alerts, and you resolve problems with Remote Actions.
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.
- Non-Events Monitoring style checks – Detect too few, too many, or too lengthy executions within the lookback period.
- Automatic Discovery – The Nodinite Azure Agent uses the Azure REST API to discover Function Apps and Functions automatically.
- Category-Based Monitoring – Group Resources by the Nodinite concept of Categories.
- Role-Based Access – Share access to individual items with Users through 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

Example: Different types of Azure Function-related Monitoring Resources and Categories in a Nodinite Monitor View.
Each Resource evaluates to a state (OK, Warning, Error, Unavailable). The Monitoring Service collects the state from the agent. 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 |
|
Review prerequisites and Functions Monitoring requirements |
| ❌ Error | Error threshold breached | ✅ Non-Events
|
|
| ⚠️ Warning | Warning threshold breached | ✅ Non-Events
|
Edit thresholds |
| ✅ OK | Within user-defined thresholds | ✅ State (Enabled) |
Set the thresholds with the Edit Remote Action, or globally in the agent Configuration.
Function Failed Executions
Nodinite evaluates the state of Function - Failed Executions Resources as follows:
| State | Status | Description | Actions |
|---|---|---|---|
| 🚫 Unavailable | Resource not available |
|
Review prerequisites |
| ❌ Error | Errors exist | At least one failed execution occurred within the lookback period | |
| ✅ 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 (Web Apps without Functions: see Monitoring Web Site):
| State | Status | Description | Actions |
|---|---|---|---|
| 🚫 Unavailable | Resource not available |
|
Review prerequisites and the firewall settings |
| ❌ Error | Errors exist | Function App (Website) is in the Stopped state | |
| ✅ OK | No problems exist | Function App (Website) is operational |
The Function App Details include run statistics that help you set the Non-Events Monitoring thresholds; see Function App Web Site Details.
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.
Frequently Asked Questions
Use the Troubleshooting guide to find answers to common questions and known issues, such as missing Remote Actions. To set up the agent, follow Prerequisites, Install, and Configuration.
Next Steps
- Manage Functions
- Configure the Azure Monitoring Agent
- Add or manage Monitor View - Share Function monitoring with your teams
Related Topics
- Azure Monitoring Agent Overview
- Azure Logging and Monitoring Overview
- Prerequisites
- Resources
- Categories
- Applications
- Monitoring Web Site
- Monitoring Application Insights
- 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



