call
Go to Console

 

 

 

Database Console Guide

 

This page provides a complete guide to using the Database entity of the Namirasoft Infra Console. You will find a detailed explanation of how database connections are configured and structured for infrastructure monitoring, along with descriptions of each field used when creating and managing Database configurations. Use this guide to understand how Database configurations allow Namirasoft Infra to collect operational data from various database systems.

 

What Is a Database?

A Database in Namirasoft Infra represents a connection configuration that allows the platform to access and structure operational data from database management systems. Database configurations define how Namirasoft Infra connects to, monitors, and collects performance metrics from your database instances, regardless of where they are deployed.

 

Database configurations enable the collection of critical operational data including query performance, connection counts, replication status, storage utilization, and error rates. This data is structured and delivered to Namirasoft Expert, where it supports intelligent monitoring, performance analysis, and automated remediation workflows for your database infrastructure.

 

Each Database configuration belongs to a specific Project and Environment, ensuring that database monitoring data remains organized according to your operational context and access requirements. Databases can be deployed in various environments such as dedicated servers, within Kubernetes clusters, or as managed cloud services, and Namirasoft Infra provides consistent monitoring through flexible connection methods.

 

The Challenge in Managing Database Monitoring

Modern applications rely on multiple database systems deployed across different environments, each with its own connection requirements, monitoring protocols, and performance characteristics. Managing database monitoring at scale presents several challenges:

 

  • Connection Complexity: Different databases require different connection methods, credentials, and network configurations

 

  • Environment Diversity: Databases running on physical servers, virtual machines, Kubernetes clusters, and cloud services need unified monitoring

 

  • Security Management: Safely handling database credentials while maintaining monitoring access

 

  • Performance Correlation: Difficulty correlating database performance with application and infrastructure metrics

 

  • Scale Issues: Manual connection configuration doesn’t scale across dozens or hundreds of database instances

 

  • Troubleshooting Complexity: Isolating database issues from application or infrastructure problems requires integrated visibility

 

While database systems provide some native monitoring capabilities, they typically lack integration with broader infrastructure monitoring and intelligent analysis systems.

 

How Namirasoft Infra Solves the Problem

Namirasoft Infra addresses database monitoring challenges through structured Database configurations that standardize how databases are connected, monitored, and integrated into the broader infrastructure observability platform.

 

Database configurations provide a flexible framework for connecting to databases regardless of their deployment environment. By offering multiple connection types (direct, via server, or via Kubernetes), Namirasoft Infra accommodates various deployment patterns while maintaining consistent monitoring capabilities.

 

Once configured, Namirasoft Infra automatically establishes secure monitoring connections, collects structured operational data, and feeds this information to Namirasoft Expert for comprehensive analysis. This enables teams to detect database performance issues early, correlate them with other infrastructure events, and leverage automated remediation for common database problems.

 

Overview of Database Fields and Options

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

 

  • ID (string): This is a unique identifier automatically assigned to the Database configuration when it is created. This is used internally to track this specific database connection.

 

  • User ID (Namirasoft Account’s ID): This is the unique identifier assigned to the Namirasoft Account user who owns the Database configuration. This is used for permission control and activity tracking.

 

  • Workspace ID (Namirasoft Workspace’s ID): This refers to a workspace created in the Namirasoft Workspace app where the Database configuration is created. This ensures the configuration is organized within the correct operational workspace.

 

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

 

  • Project (Enum): This field specifies which Project the Database configuration belongs to. A Project is a logical container that groups related infrastructure components together.

 

You must create a Project before creating a Database 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 Database operates within. An Environment represents a stage in your development lifecycle.

 

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

 

  • 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 Database configurations, this Log Group will contain database logs, query logs, and error logs.

 

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.

 

  • Database Type (Enum): This field specifies which type of database system you are connecting to. Selecting the correct database type ensures proper integration with database-specific monitoring features and metrics collection. Different database types have different monitoring requirements, performance characteristics, and query languages.

 

    • ClickHouse: ClickHouse is a column-oriented database management system designed for online analytical processing (OLAP) and real-time analytics. It excels at handling large volumes of data for analytical queries.

 

    • ElasticSearch: ElasticSearch is distributed search and analytics engine built for full-text search, log analysis, and real-time data exploration. It’s commonly used for log and event data analysis.

 

    • MongoDB: MongoDB is a document-oriented NoSQL database that stores data in flexible, JSON-like documents. It’s designed for scalability and handling unstructured or semi-structured data.

 

    • MySQL: MySQL is a popular open-source relational database management system that uses Structured Query Language (SQL). It’s widely used for web applications and online transaction processing (OLTP).

 

    • PostgreSQL: PostgreSQL is an advanced open-source relational database system with strong emphasis on extensibility and SQL compliance. It supports complex queries, foreign keys, triggers, and transactional integrity.

 

  • Connect Type (Enum): This field specifies how Namirasoft Infra will connect to the database. The connection type determines what additional configuration will be required and how the monitoring agent accesses the database.

 

    • Direct: Connect directly to the database using its network address (host and port). Use this option when:

 

      • The database is publicly accessible with a fixed IP or hostname

 

      • Namirasoft Infra has direct network access to the database

 

      • You don’t need to route through a Server or Kubernetes cluster.

 

    •  By Server: Connect to the database through a Server resource. Use this option when:

 

      • The database is running on or accessible only through a specific server

 

      • You need to use SSH tunneling or agent-based monitoring on the server

 

      • The database isn’t directly accessible from the Namirasoft Infra network

 

When you select “By Server,” you will need to select which Server configuration to use. The Server must have network access to the database and may require additional configuration for database monitoring.

 

    • By Kubernetes: Connect to the database through a Kubernetes cluster. Use this option when:

 

      • The database is running as a container inside a Kubernetes cluster

 

      • The database is managed by a Kubernetes operator or deployed via Helm

 

      • You need to access the database through Kubernetes service discovery

 

When you select “By Kubernetes,” you will need to select which Kubernetes configuration to use. The Kubernetes cluster must have the database running and accessible via Kubernetes services.

 

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

 

  • Database Credential ID (String): This is the unique identifier of the credential set used to connect to the database. This references securely stored authentication information (username, password, certificates, etc.) without exposing the actual credentials. The system creates this automatically when you configure database credentials.

 

  • Connect Server ID (String): If the Connect Type is “By Server,” this field contains the unique identifier of the Server resource used for the connection. This links the Database configuration to the specific Server entity.

 

  • Connect Kubernetes ID (String): If the Connect Type is “By Kubernetes,” this field contains the unique identifier of the Kubernetes configuration used for the connection. This links the Database configuration to the specific Kubernetes entity.

 

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

 

  • Updated At (DateTime): This shows the date and time when the Database configuration was last updated. The value changes automatically whenever configuration details are modified or when significant changes to the database connection occur.

Keep Your Infrastructure Running Smoothly and Reliably

Get Started Now Explore Console Guide