Project Console Guide

This page provides a complete guide to using the Project entity of the Namirasoft Infra Console. You will find a detailed explanation of how Projects organize infrastructure and service monitoring, along with descriptions of each field used when creating and managing Projects. Use this guide to understand how Projects define operational boundaries and structure monitoring data across your infrastructure.

What Is a Project?

A Project in Namirasoft Infra represents the highest-level logical container used to group infrastructure platforms, application services, monitoring workflows, and operational data under a single operational objective.

 

Projects typically represent a complete system, application platform, product, or service ecosystem. They define the primary boundary used to organize infrastructure visibility, monitoring configurations, and automated operational workflows.

 

All infrastructure resources, services, monitoring rules, and operational signals must belong to a Project. By grouping related components under a Project, teams can maintain clear separation between systems, improve monitoring clarity, and reduce operational complexity.

 

Projects provide organizational structure and monitoring context for infrastructure and services operating within them.

 

The Challenge in Managing Infrastructure Scope

Modern infrastructure environments often support multiple applications, services, and operational systems simultaneously. These systems may share cloud platforms, servers, Kubernetes clusters, and runtime environments, making it difficult to separate monitoring data and operational workflows between them.

 

Without clear logical boundaries, organizations may face several challenges:

 

• Monitoring data from unrelated systems becomes mixed together

 

• Incident investigation becomes more difficult due to lack of system separation

 

• Automation workflows may incorrectly affect unrelated infrastructure

 

• Operational ownership and access control become harder to manage

 

• Service dependency visibility becomes fragmented

 

Although infrastructure platforms provide resource-level organization, they often do not provide consistent operational grouping across multiple infrastructure layers and service components.

 

How Namirasoft Infra Solves the Problem

Namirasoft Infra addresses infrastructure scope challenges by introducing Projects as a centralized operational grouping layer.

 

Projects allow teams to organize infrastructure platforms, services, monitoring configurations, and operational workflows into clearly defined system boundaries. This structure ensures monitoring data remains properly grouped, improves investigation clarity, and supports reliable automation workflows through Namirasoft Expert.

 

By defining Projects before configuring infrastructure and services, organizations can maintain consistent monitoring separation, improve operational visibility, and reduce configuration errors across distributed environments.

 

 

Overview of Project Fields and Options

Below is a detailed explanation of the fields available when creating or managing a Project. Understanding these fields helps ensure infrastructure and service data is properly organized, which improves monitoring accuracy, investigation clarity, and automated operational workflows.

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

• User ID (Namirasoft Account’s ID): This is the unique ID assigned to a user of the Namirasoft Account, which gives access to all Namirasoft apps. This ties the Project to a specific user (for access control and tracking). It is used in the backend to manage permissions and history.

• Workspace ID (Namirasoft Workspace’s ID): This refers to a workspace created in the Namirasoft Workspace app, which allows users to group projects, teams, or environments. This ensures that each Project is tied to the correct workspace.

• Name (String): This is a human-friendly label for the Project. Choosing a descriptive name helps teams quickly identify each Project. The Project name does not affect infrastructure behavior or monitoring logic.

• Description (String): Descriptions help teams document the purpose, operational scope, ownership details, or special configuration considerations related to the Project. Although this field does not affect monitoring or automation behavior, it improves documentation clarity and helps teams understand the intent behind Project configurations.

• Created At (DateTime): This shows the date and time when the Project was originally created. This value is automatically assigned by the system and cannot be modified.

• Updated At (DateTime): This shows the date and time when the Project configuration was last modified. The value updates automatically whenever Project details such as Name or Description are changed.