- 4 minutes to read

Monitoring Container Apps in Azure

Take full control of your Azure Container Apps with Nodinite. Detect stopped apps, automate discovery, and let your team act before problems impact your business, all without direct Azure Portal access.

  • ✅ Detect stopped Container Apps and receive alerts through Alarm Plugins
  • ✅ Discover and monitor all Azure Container Apps and Environments automatically
  • ✅ Share secure, role-based access with your team through Monitor Views
  • ✅ Start and Stop Container Apps with Remote Actions

Use Nodinite to manage and monitor Azure Container Apps and Environments for business agility and operational excellence.

This page explains how the Nodinite Azure Agent monitors Container Apps and presents them in one or more role-based Monitor Views. Nodinite tracks Container App configuration and lets you manage the set of Resource Groups to monitor. Use remote commands as Actions to resolve issues swiftly; the Managing Container App page details the Remote Actions.

Azure Container Apps as Resources in a Monitor View
Example: Monitored Container Apps in a Nodinite Monitor View.

How Container App Monitoring Works

The Azure Agent reads each Container App and Container Apps Environment through the Azure REST API, evaluates the state, and reports it to the Nodinite Monitoring Service. State changes reach your team through Alarm Plugins, and users act on them from the Web Client.

graph LR CA["fa:fa-container-storage Container Apps
and Environments"] -->|"REST API"| AG["fa:fa-monitor-waveform Azure Agent"] AG --> OK["fa:fa-check OK
App running"] AG --> WA["fa:fa-triangle-exclamation Warning
Environment has no apps"] AG --> ER["fa:fa-xmark Error
App stopped"] AG --> UN["fa:fa-ban Unavailable
Cannot evaluate"] WA --> AP["fa:fa-bell Alarm Plugins"] ER --> AP ER --> RA["fa:fa-play Start App"] 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 Azure Agent evaluates each Container App and Environment into OK (green), Warning (yellow), or Error and Unavailable (red); Warning and Error raise alerts, and you start a stopped app with a Remote Action.

Monitoring Features

  • State Evaluation – Assess Container App health based on policy.

    If Nodinite cannot check your Container App state, no one else can use them either.

  • Environments – Monitor all Container Apps Environments.
  • Automatic Discovery – The Nodinite Azure Agent uses the Azure REST API to present Container Apps automatically.
  • Category-based Monitoring – Nodinite groups monitored Resources by Categories.
  • Role-based Access – Share access to individual items with Users through Monitor Views.

Azure Container App

Nodinite presents each Container App as a Resource. For example, if you have three Container Apps, you see three Resources in Nodinite.

  • The Nodinite Resources name matches the Container App name in the Azure Portal.
  • Monitored Container Apps belong to the 'Azure Container App' Category.
  • The Application name uses the pattern: Display Name from the Configuration.

Many other Azure-related Categories exist. Review the Azure Logging and Monitoring Overview user guide.

Each item (shown as a Resource) receives a state (OK, Warning, Error, Unavailable) based on evaluation. Override the evaluation for any Nodinite Resource with the Expected State option, for example for a Container App you keep stopped on purpose.

State Evaluation for Azure Container App

For Container App Resources, Nodinite evaluates state as follows:

State Status Description Actions
🚫 Unavailable Resource not available
  • Nodinite cannot evaluate the 'Container App' due to network or security issues
 Review prerequisites
❌ Error Error threshold breached The Container App is stopped View Details
Start App
✅ OK Within user-defined thresholds The Container App runs as expected View Details
Logs
Stop App

When the state is Unavailable, check the Azure rights of the App Registration and the firewall settings in the Prerequisites.

Environment

Nodinite monitors each Azure Container Apps Environment as a Resource.

Container Apps Environment Resource in a Monitor View
Example: Environment Resource in a Nodinite Monitor View.

State Evaluation for Azure Container App - Environment

For Container App - Environment Resources, Nodinite evaluates state as follows:

State Status Description Actions
🚫 Unavailable Resource not available
  • Nodinite cannot evaluate the 'Container App' due to network or security issues
 Review prerequisites
⚠️ WarningNew 6.2.0.5 Warning threshold breached No Container App exists in the Environment View Details
✅ OK Within user-defined thresholds At least one Container App exists in the Environment View Details

Alert History for Container App

Analyze the alert history for your Container Apps in Nodinite. During root cause analysis, search for historical state changes for any time span, either for all Container Apps or individually, if your Monitor View allows it. Learn more in the Add or manage Monitor View guide and the Resource State History user guide.

Search Resource history Container App Resource history Container App Environment
Search for alert history for all resources in the Monitor View
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.		 Alert history for the selected Container App Environment
Alert history for the selected Container App Environment.

Frequently Asked Questions

Use the Troubleshooting guide to find answers to common questions and known issues.

Next Steps