Monitoring Functions in Azure
Don't let your business down! Monitor all your Azure Functions and gain access to details without the Azure portal.
Failed Functions
Non-Events (Too frequent, too few, too lengthy)
Managing Functions
Category Based Monitoring
On this page, you learn about Azure Function Monitoring options using Nodinite from one or more role-based Monitor Views. Nodinite monitors the Functions. You can manage the monitoring thresholds for the Function; Remote commands are available as Actions to help you swiftly address reported problems. The Remote Actions are detailed on the Managing Function page.
Example list of monitored Functions in a Nodinite Monitor View.
Monitoring Features
- State Evaluation - Provide state evaluation according to pre-defined policy.
If Nodinite can't check the state of your Functions, chances are no one else can use them either.
- Automatic Discovery of Function Apps and Functions.
- The Nodinite Azure Agent makes use of the Azure Rest API. Hence, Function Apps (Website) and Functions present automatically.
- Category-based monitoring - Resources group by the Nodinite concept of Categories.
- Share access to individual items from within Nodinite using one or more role-based Monitor Views.
State evaluation for Functions
The Functions to monitor manifests within Nodinite as one or more Resources. For example, if you have three Functions, you will have three Resources in Nodinite.
- The Nodinite Resources name is the same as the deployed Function name.
- Monitored Functions belong to 'Function' Category:
Many other Azure-related Categories exist as well, please review the Azure Logging and Monitoring Overview
- The Application name is created with the following pattern:
Configuration name/Resource Group Name
Each item (presented in Nodinite as a Resource) evaluates with a state (i.e. OK, Warning, Error, Unavailable).
You can override the evaluation process by configuring the Expected State option available for all Nodinite Resources.
Function
For Function Resources, the state evaluates as described in the table below:
State | Status | Description | Actions | |
---|---|---|---|---|
Unavailable | Resource not available |
|
Review prerequisites | |
Error | Error threshold is breached | Non-Events
|
||
Warning | Warning threshold is breached | Non-Events
|
||
OK | Within user-defined thresholds | State (Enabled) |
Function Failed Executions
For Function - Failed Executions Resources, the state evaluates as described in the table below:
State | Status | Description | Actions | |
---|---|---|---|---|
Unavailable | Resource not available |
|
Review prerequisites | |
Error | Errors exist | At least one failed execution exists within the lookback period | ||
OK | No failed executions | There are no failed executions within the lookback period |
Function App Web Site
For Web Site - Function App Resources, the state evaluates as described in the table below:
State | Status | Description | Actions | |
---|---|---|---|---|
Unavailable | Resource not available |
|
Review prerequisites | |
Error | Errors exist | Function App (Website) is in the Stopped state | ||
OK | No problems exist | Function App (Website) is operational |
Alert history for Function
During root cause analysis or for other purposes, it might be helpful to understand how often your Function problems occur. If your Monitor View allows it, you can search for historical state changes for the selected lookback period for all your Functions or individually. The generic instructions on the 'Add or manage Monitor View' page further detail this topic.
Search | Function history | Failed Function history | Web Site - Function App history |
---|---|---|---|
Search for alert history for all resources in the Monitor View | Alert history for the selected Function item | Alert history for the selected Failed Function item | Alert history for the selected 'Web Site - Function App' item |
Frequently asked questions
Use the troubleshooting guide to find the FAQ and answers to known problems.