call
Go to Console

 

 

 

Server Console Guide

 

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

 

What Is a Server?

A Server in Namirasoft Infra represents a physical or virtual machine that hosts applications, services, or infrastructure components. Server configurations define how Namirasoft Infra connects to, monitors, and collects operational data from individual server instances across your infrastructure.

 

Server configurations enable the collection of key operational metrics including CPU utilization, memory usage, disk I/O, network traffic, and process-level activity. This data is structured and delivered to Namirasoft Expert, where it supports intelligent monitoring, performance analysis, and automated remediation workflows.

 

Each Server configuration belongs to a specific Project and Environment, ensuring that server monitoring data remains organized according to your operational context and access requirements. Servers can be deployed in various cloud platforms, on-premises data centers, or hybrid environments, with Namirasoft Infra providing consistent monitoring regardless of deployment location.

The Challenge in Managing Server Infrastructure

Modern infrastructure environments typically consist of dozens to thousands of server instances distributed across multiple locations, cloud providers, and deployment models. Each server may have different operating systems, configurations, access methods, and monitoring requirements.

 

Without a centralized server management approach, organizations often face several challenges:

 

  • Inconsistent Monitoring: Different monitoring tools or agents deployed across server types lead to fragmented visibility

 

  • Manual Configuration: Server setup and monitoring configuration requires repetitive manual work for each instance

 

  • Access Management Complexity: Managing SSH keys, credentials, and firewall rules across hundreds of servers becomes error-prone

 

  • Performance Correlation Issues: Isolating performance problems across interdependent servers requires manual investigation

 

  • Scale Limitations: Manual approaches don’t scale efficiently as server counts grow into the hundreds or thousands

 

Although operating systems provide basic monitoring capabilities and cloud platforms offer their own monitoring services, they typically lack cross-environment consistency and integration with intelligent analysis systems.

 

How Namirasoft Infra Solves the Problem

Namirasoft Infra addresses server management challenges through structured Server configurations that standardize how servers are connected, monitored, and integrated into the broader infrastructure observability platform.

 

Server configurations provide a consistent interface for connecting to servers regardless of their deployment environment. Once configured, Namirasoft Infra automatically discovers server characteristics, establishes secure monitoring connections, and begins collecting structured operational data. This data flows into Namirasoft Expert, where it contributes to comprehensive infrastructure analysis and automated operational workflows.

 

By treating Servers as first-class entities within the monitoring platform, Namirasoft Infra enables teams to maintain consistent visibility, automate configuration management, and leverage intelligent analysis across their entire server estate.

 

Overview of Server Fields and Options

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

 

  • ID (string): This is a unique identifier automatically assigned to the Server configuration when it is created. Think of this as a serial number that the system uses internally to track this specific server. 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 Server configuration. It is used internally for permission control and activity tracking.

 

  • Workspace ID (Namirasoft Workspace’s ID): This refers to a workspace created in the Namirasoft Workspace app, which identifies the workspace where the Server configuration is created. A workspace is like a digital office space where teams organize their projects and infrastructure.

 

  • Service User ID (string): This is an internal identifier used by Namirasoft Infra to manage service-level access to the server. Think of this as a special service account that Namirasoft Infra uses to securely connect to and monitor your server without requiring your personal credentials to be stored or exposed.

 

  • Service Session ID (string): This is a unique session identifier generated for each monitoring connection to the server. Similar to a unique meeting ID for a video call, this identifier ensures secure, traceable communication between Namirasoft Infra and the server instance for each monitoring session.

 

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

 

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

 

    • 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 Server belongs to. A Project is a logical container that groups related infrastructure components together, similar to how a folder organizes related files. This helps with access control, billing, and management organization.

 

You must create a Project before creating a server. 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 Server operates within. An Environment represents a stage in your development lifecycle, such as production (live systems), staging (testing before production), or development (early development work). Separating environments prevents accidental changes to live systems.

 

You must create an Environment before creating a server. 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.

 

  • Log Group (Enum): A Log Group is a logical container that stores and organizes log files from your applications and systems in Namirasoft Log. You can assign a unique name and configure how long logs should be kept (retention period) for each Log Group.

 

You can click the “+” icon next to this field to create a new Log Group if one doesn’t exist. For more information about Log Groups and log management, visit Namirasoft Log.

 

  • Metric Retention Value (Integer): This field specifies how long metric data (performance measurements like CPU usage, memory usage, etc.) should be kept for this server. The number you enter here works together with the Metric Retention Unit to determine the total retention period.

 

  • Metric Retention Unit (Enum): This field specifies the time unit for metric retention, working with the Metric Retention Value to define how long metric data is stored. This setting determines whether your metrics are kept for days, months, or years.

 

  • Description (String): This field allows you to document the purpose, role, or special characteristics of the server. It helps teams understand the server’s function within the infrastructure (for example, “Primary database server for customer orders” or “Development server for the mobile app team”).

 

  • IP Public (String): This field displays the public IP address of the server, as discovered by Namirasoft Infra during the initial connection. A public IP address is like a street address for the internet; it’s how other systems on the internet can find and communicate with your server.

 

  • IP Private (String): This field displays the private IP address of the server, as discovered within its internal network. A private IP address is like an internal extension number in an office building; it’s used for communication between systems within the same private network but isn’t accessible from the public internet.

 

  • Architecture (String): This field displays the CPU architecture of the server (e.g., x86_64, arm64), automatically detected during the initial connection. CPU architecture refers to the design and instruction set of the processor, which determines what kind of software can run on the server.

 

  • OS (String): This field displays the operating system name and version running on the server (e.g., Ubuntu 20.04, CentOS 8, Windows Server 2022), automatically detected during connection establishment. The operating system is the foundational software that manages the server’s hardware and provides services for other applications.

 

  • CPU (String): This field displays information about the server’s CPU (Central Processing Unit) configuration, including model, core count, and clock speed, collected during the initial inventory scan. The CPU is the “brain” of the server that performs calculations and runs programs.

 

  • GPU (String): This field displays information about any GPU (Graphics Processing Unit) hardware present on the server, including model and memory capacity, when applicable. GPUs are specialized processors often used for graphics rendering, machine learning, or scientific computations.

 

  • Memory (String): This field displays the total physical memory (RAM) available on the server, expressed in appropriate units (GB, MB). RAM (Random Access Memory) is the short-term memory where the server stores data it’s actively using for faster access.

 

  • Disk (String): This field displays information about the server’s disk configuration, including total storage capacity and partition layout. This refers to the permanent storage (like hard drives or SSDs) where the operating system, applications, and data are stored.

 

  • CPU Usage (Percentage): This field displays the current CPU utilization percentage, updated regularly by the monitoring agent or connection. This shows how much of the server’s processing power is currently being used, similar to how a car’s tachometer shows engine RPM.

 

  • Memory Usage (Percentage): This field displays the current memory utilization percentage, updated regularly by the monitoring agent or connection. This shows how much of the server’s RAM is currently in use by applications and the operating system.

 

  • Disk Usage (Percentage): This field displays the current disk utilization percentage for the primary storage volume, updated regularly by the monitoring agent or connection. This shows how much of the server’s storage capacity is currently filled with data.

 

  • Last Sync (DateTime): This field shows the date and time when Namirasoft Infra last successfully synchronized data from the server. This indicates the freshness of the collected metrics and inventory information.

 

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

 

  • Updated At (DateTime): This shows the date and time when the Server configuration was last updated. The value changes automatically whenever configuration details are modified.

Keep Your Infrastructure Running Smoothly and Reliably

Get Started Now Explore Console Guide