Monitoring App Registrations in Azure
Don't let your business down! Get alerts for ageing secrets in App Registrations and gain access to details without the Azure portal.
This page provides documentation about App Registration Monitoring options using Nodinite from one or more role-based Monitor Views. Nodinite monitors the age of App Registrations. You can manage the monitoring thresholds for the App Registration; Remote commands are available as Actions to help you swiftly address reported problems. The Remote Actions are detailed on the Managing App Registration page.
Example list of monitored App Registrations in a Nodinite Monitor View.
Monitoring Features
- State Evaluation - Provide state evaluation according to pre-defined policy.
If Nodinite can't check your App Registration items' state, chances are no one else can use them either.
- Automatic Discovery of App Registrations.
- The Nodinite Azure Agent makes use of the Azure Rest API. Hence, App Registrations presents automatically.
- Category-based monitoring - The monitored Resources groups 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 App Registrations
The App Registrations to monitor manifests within Nodinite as one or more Resources. For example, if you have three App Registrations, you will have three Resources in Nodinite.
- The Nodinite Resources name is the same as the deployed App Registration name.
- Monitored App Registrations belong to 'App Registration' Category:
Many other Azure related Categories exists as well, please review the Azure Logging and Monitoring Overview
- The Application name is created with the following pattern:
Subscription 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.
App Registration
For App Registration 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 |
|
Edit | |
| Warning | Warning threshold is breached |
|
Edit | |
| OK | Within user-defined thresholds |
|
Details |
Note
To gain some performance and ease the stress on the system, information about the current set of App Registrations is being cached for five minutes. If you make a change in Azure, please allow a few minutes for the agent to synchronize with fresh data.
Alert history for App Registration
During root cause analysis or other purposes, it might be helpful to understand how often your App Registration problems happen. If your Monitor View allows it, you can search for historical state changes for the provided time-span either for all your App Registration or individually. This topic is further detailed within the generic instructions on how to Add or manage Monitor View page.
| Search | Resource history |
|---|---|
 Search for alert history for all resources in the Monitor View |
 Alert history for the selected App Registration item |
Frequently asked questions
Use the troubleshooting guide to find the FAQ and answers to known problems.
Insufficent Privilges
New 6.2.0.2
If you see a Resource like the one depicted in the image below; your App Registration lacks the right to read information about App Registrations. Please review the
Azure Access page, least privileges section.
