- 3 minutes to read

Monitoring Container Apps in Azure

Manage the set of Azure services to Monitor using the Nodinite Container Apps resource.

This page provides documentation about Container App Monitoring options using Nodinite from one or more role-based Monitor Views. Nodinite monitors Container App configuration. You can manage the set of Resource Groups to monitor for configured Container Apps; Remote commands are available as Actions to help you swiftly address reported problems. The Remote Actions are detailed on the Managing Container App page.
Container App as Resources
Example list of monitored Container Apps in a Nodinite Monitor View.

Monitoring Features

  • State Evaluation - Provide state evaluation according to a pre-defined policy.

    If Nodinite can't check your Container App items' state, chances are no one else can use them either.

  • Environments are featured in the Monitoring.
  • The configured Container Apps are monitored
  • 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.

Azure Container App

The Container Apps to monitor manifests within Nodinite as one or more Resources. For example, if you have three Container Apps, you will have three Resources in Nodinite.

  • The Nodinite Resources name is the same as Container App from within the Azure portal.
  • Monitored Container Apps belong to the 'Azure Container App' Category:

Many other Azure related Categories exists as well. Review the Azure Logging and Monitoring Overview user guide.

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.

State evaluation for Azure Container App

For the Container App Resources, the state evaluates as described in the table below:

State Status Description Actions
Unavailable Resource not available
  • Evaluation of the 'Container App' is not possible either due to network or security-related problems
 Review prerequisites
Error Error threshold is breached The Container App is in the Stopped state Details
Start
OK Within user-defined thresholds The Container App is operational Details
Stop

Environment

Each Azure Container App Environment is one Resource in Nodinite.
Environment Resource
Here's an example of an Environment Resource in a Nodinite Monitor View.

State evaluation for Azure Container App - Environment

For the Container App - Environment Resources, the state evaluates as described in the table below:

State Status Description Actions
Unavailable Resource not available
  • Evaluation of the 'Container App' is not possible either due to network or security-related problems
 Review prerequisites
WarningNew 6.2.0.5 Warning threshold is breached There is no Container App in the Environment Details
OK Within user-defined thresholds There is at least one Container App in the Environment Details

Alert history for Container App

During root cause analysis or other purposes, it might be helpful to understand how often your Container App problems happen. If your Monitor View allows it, you can search for historical state changes for the provided time-span either for all your Container App or individually. This topic is further detailed within the generic instructions on how to Add or manage Monitor View page.

Search Resource history Container App Resource history Container App Environment

Search for alert history for all resources in the Monitor View
Alert history for the selected Container App.
Alert history for the selected Container App Environment.

Frequently asked questions

Use the troubleshooting guide to find the FAQ and answers to known problems.

Next step