- 3 minutes to read

Monitoring Container Apps in Azure

Take full control of your Azure Container Apps with Nodinite. Instantly detect issues, automate discovery, and empower your team to act before problems impact your business—all without direct Azure portal access.

✅ Instantly detect and receive alerts for issues in Container Apps
✅ Automate discovery and monitoring of all Azure Container Apps and Environments
✅ Empower secure, role-based access for your team
✅ Take action with remote commands and proactive alerts

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

This page explains how Nodinite monitors Container Apps from one or more role-based Monitor Views. Nodinite tracks Container App configuration and lets you manage the set of Resource Groups to monitor. You can use remote commands as Actions to swiftly resolve issues. Find details about Remote Actions on the Managing Container App page.

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

Monitoring Features

  • State Evaluation – Instantly 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 App Environments.
  • Automatic Discovery – Nodinite Azure Agent uses the Azure Rest API to automatically present Container Apps.
  • Category-based Monitoring – Group monitored Resources by Nodinite Categories.
  • Role-based Access – Share access to individual items using 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.

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.

You can override the evaluation process by configuring the Expected State option for any Nodinite [Resource][].

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
Stop App

Environment

Nodinite monitors each Azure Container App Environment as a Resource.
Environment Resource
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

Nodinite enables you to analyze alert history for your Container Apps. During root cause analysis, you can 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.

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.

Frequently Asked Questions

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

Next Step