Docker Console Guide

This page provides a complete guide to using the Docker entity of the Namirasoft Infra Console. You will find a detailed explanation of how Docker containers and hosts are connected and structured for infrastructure monitoring, along with descriptions of each field used when creating and managing Docker configurations. Use this guide to understand how Docker connections allow Namirasoft Infra to collect operational data from container runtime environments.

What Is a Docker?

A Docker in Namirasoft Infra represents a connection configuration that allows the platform to access and structure operational data from Docker containers and container hosts. Docker is a platform that enables developers to build, package, and run applications in isolated software containers.

 

Docker configurations in Namirasoft Infra serve a specific purpose: they define how the platform connects to and monitors Docker container runtime environments. Unlike Kubernetes configurations that manage container orchestration (scheduling and scaling across multiple machines), Docker configurations focus on the container runtime itself – the engine that runs individual containers on a single host.

 

These configurations enable Namirasoft Infra to collect data about container performance, resource usage, image details, and runtime status. This information is structured and delivered to Namirasoft Expert for analysis alongside other infrastructure data, providing complete visibility into your containerized workloads at the runtime level.

The Challenge in Managing Docker Container Runtimes

While containerization simplifies application deployment, managing and monitoring Docker runtime environments presents unique challenges:

 

• Host-Level Visibility Gap: Understanding how containers impact the underlying host system

 

• Performance Isolation Issues: Difficulty determining if performance problems originate from containers or the host

 

• Resource Allocation Conflicts: Containers competing for CPU, memory, and I/O resources without clear visibility

 

• Connection Complexity: Different methods needed to monitor containers based on their deployment (local, remote, cloud)

 

• Scale Management: Monitoring hundreds of containers across multiple hosts becomes increasingly complex

 

• Runtime-Specific Issues: Problems unique to Docker runtime that don’t appear in orchestration layer monitoring

 

Traditional monitoring tools often treat containers as black boxes or focus only on the applications inside them, missing critical runtime-level insights that affect stability and performance.

How Namirasoft Infra Solves the Problem

Namirasoft Infra addresses Docker runtime monitoring challenges through structured Docker configurations that provide direct visibility into container runtime environments.

 

Docker configurations establish a secure connection to Docker hosts, enabling Namirasoft Infra to collect detailed operational data at the runtime level. This includes container performance metrics, image information, volume usage, network configuration, and daemon health. This runtime-level data complements orchestration-level data from Kubernetes, providing a complete picture of your container environment from runtime to orchestration.

 

By treating Docker as a distinct monitoring entity, Namirasoft Infra enables teams to detect runtime-specific issues, optimize resource allocation at the container engine level, and maintain visibility into container environments that may not be managed by orchestration systems.

Overview of Docker Fields and Options

Below is a detailed explanation of the fields available when creating or managing a Docker configuration. Understanding these fields helps ensure your Docker runtime environments are properly connected and structured for monitoring and operational analysis.

• ID (string): This is a unique identifier automatically assigned to the Docker configuration when it is created. Users cannot modify or manually define this value.

• User ID (Namirasoft Account’s ID): This is the unique identifier assigned to the Namirasoft Account user who owns the Docker configuration. It is used internally to track who created and has access to this Docker monitoring setup.

• Workspace ID (Namirasoft Workspace’s ID): This refers to a workspace created in the Namirasoft Workspace app, which identifies the workspace where the Docker configuration is created. This ensures your Docker monitoring is organized within the correct workspace.

• Service User ID (string): This is an internal identifier representing a service-level account used by Namirasoft Infra to securely access and monitor the Docker host or Docker runtime environment. This service identity allows automated monitoring without storing or exposing personal user credentials.

• Service Session ID (string): This is a unique session identifier generated for each monitoring connection between Namirasoft Infra and the Docker runtime environment. It enables secure, traceable communication and helps track monitoring sessions and API interactions.

• Name (String): This is a human-readable label used to identify the Docker configuration. The name helps teams distinguish between multiple Docker environments.

• Cloud (Enum): This field specifies which cloud provider hosts the Docker environment. Selecting the correct provider ensures proper integration with cloud-specific features and metadata.

• • AWS (Amazon Web Services): Amazon Web Services is a cloud computing platform providing infrastructure services such as virtual servers, storage, networking, and managed application services.

• • GCP (Google Cloud Platform): Google Cloud Platform provides cloud infrastructure services including computing, container orchestration, storage, and distributed application services.

• • Azure (Microsoft Azure): Microsoft Azure is a cloud computing platform that provides infrastructure, platform services, and application hosting environments.

• • Other: This option is used when connecting private cloud environments or cloud providers that are not AWS, GCP, or Azure. Users typically select this option for custom infrastructure or unsupported cloud platforms.

• Project (Enum): This field specifies which Project the Docker configuration belongs to. A Project is a logical container that groups related infrastructure components together, similar to how a folder organizes related files.

You must create a Project before creating a Docker configuration. If no Project exists, you can click the “+” icon next to this field, which redirects you to the Project configuration page. For more information about Projects, visit the Project Console Guide.

• Environment (Enum): This field specifies which Environment the Docker operates within. An Environment represents a stage in your development lifecycle, such as production (live systems), staging (final testing), or development (early development work).

You must create an Environment before creating a Docker configuration. If no Environment exists, you can click the “+” icon next to this field, which redirects you to the Environment configuration page. For more information about Environments, visit the Environment Console Guide.

• Docker Server CLI ID (String): This field specifies which Server resource Namirasoft Infra uses to run Docker commands and access the Docker runtime environment. The selected Server must have Docker installed and running, as it acts as the access point through which Namirasoft Infra communicates with the Docker daemon.

What Is Docker CLI? Docker CLI (Command Line Interface) is the command-line tool used to interact with Docker daemons. It allows systems to manage containers, images, networks, and volumes. Namirasoft Infra uses Docker CLI commands to collect container runtime data, inspect container status, and gather performance metrics directly from the Docker engine.

The selected Server must have:

• • Docker installed

• • Docker daemon running

• • CLI access to Docker runtime

If you have not added your Servers in Namirasoft Infra, you can click on “+” icon and add it from the Server entity. For more information, visit Server Console Guide.

• Log Group (Enum): A Log Group is a logical container that stores and organizes log files from your applications and systems in Namirasoft Log. For Docker configurations, this Log Group will contain logs from Docker containers and the Docker daemon itself.

You must select an existing Log Group for this field. If no Log Group exists, you can click the “+” icon next to this field to create a new one. For more information about Log Groups and log management, visit Namirasoft Log.

• Description (String): This field allows you to document the purpose, role, or special characteristics of the Docker configuration. It helps teams understand the Docker environment’s function within your infrastructure

• IP Public (String): This displays the public IP address of the server hosting the Docker runtime environment, as discovered by Namirasoft Infra during connection. This represents the external network address of the Docker host machine.

• Meta Collective (JSON): This field Contains raw metadata automatically collected from the Docker runtime environment. This may include:

• • Docker engine version

• • Container inventory

• • Image information

• • Network configurations

• • Volume configuration

• • Runtime settings

• Meta Derivative (JSON): This field contains computed metrics and analytical insights generated from collected Docker runtime data. These insights may include:

• • Resource utilization trends

• • Container performance metrics

• • Runtime health indicators

• • Capacity analysis

• Last Seen At (DateTime): This displays the most recent time Namirasoft Infra detected activity or communication from the Docker runtime environment.

• Last Online At (DateTime): This displays the most recent time the Docker runtime environment was confirmed to be reachable and operating normally.

• Last Offline At (DateTime): This displays the most recent time the Docker runtime environment became unreachable or experienced connectivity or operational failure.

• Created At (DateTime): This shows the date and time when the Docker configuration was initially created. This value is automatically generated and cannot be modified.

• Updated At (DateTime): This shows the date and time when the Docker configuration was last modified or refreshed. This helps track configuration changes over time.