Monitoring Logic Apps
This section describes what's being monitored and the rules for how Nodinite translates this into meaningful monitoring states. Also, some remote commands are available as Actions to help you swiftly manage problems. Actions are further detailed in the Managing Logic Apps page.
The agent auto discovers your deployed Logic Apps in all accessible Resource Groups. Simply deploy new Logic Apps and they will automatically get monitored and listed within your Monitor Views
- Automatic Discovery
- Nodinite Azure agents make use of the Azure Rest API and offers you automatic discovery of your Logic Apps. Sharing access to to any individual Logic App is very easy from within Nodinite.
- State Evaluation - sure the Logic Apps has the intended run-time state
- Enabled/Disabled - Provides means to get you alerted if anyone disables your logic app
- Last run evaluation - monitors the outcome of runs
If Nodinite can't check the state of your Logic Apps, chances are no one else can either
List of categories being monitored
List of Logic Apps in a Monitor View
One Logic App will be displayed within Nodinite as one Resource. If you have 42 deployed Logic Apps, then you will have 42 Resources in Nodinite.
- All Logic Apps belongs to the 'Logic App' category
- The Application name is based on physical deployment paths. This pattern guarantees uniqueness:
- subscription name/resource group name/logic app name
Example of Application naming pattern
Each Logic App Resource can have one of the following states at any given moment:
- OK - Used to indicate normal operation (Enabled)
- Error - Used to indicate an error/fatal condition (Disabled)
- Unavailable - Used to indicate an error/fatal condition usually since the Monitoring or Resource is not available or can't be reached
Logic app when not available
The evaluated state may be reconfigured using Expected State override setting that exists on every Resource within Nodinite.
The Nodinite Monitoring Agent for Logic Apps evaluates the outcome of runs. There will be one virtual resource available within Monitor Views where this resource is included.
List of resources of category 'last runs' for each Logic Apps in a Monitor View
Whenever a run has failed, the Resource is evaluated as being in state Error. It will remain in this state until the error is cleared.
During root cause analysis or for other purposes it might be useful to understand how often problems with your Logic Apps happens. If your Monitor View allows it, you can search for historical state changes for the provided time span either for all your Logic Apps or individually. This topic is further detailed within the generic instructions on how to Add or manage Monitor View page.
Search for alert history for all resources in the Monitor View
Alert history for selected logic app
Other common problems and FAQ for the Logic Apps Logging and Monitoring agent can be found in the troubleshooting guide
This topic is detailed in the User access to logic apps monitoring guide
This topic is detailed in the 'User access to logic apps logging' guide
In order to Monitor Logic Apps, the Agent must be configured with the Enable monitoring checkbox checked (default is checked) further detailed in the 'User access to logic apps monitoring' page.
Image below was taken from the remote configuration form available from the Monitoring Agent Configuration administration page.
Example with monitoring for Logic Apps enabled