call
Go to Console

 

 

 

Metric Console Guide

 

This page provides a complete guide to using the Metric section of the Namirasoft Infra Console. You will find a detailed explanation of how metric collection endpoints are configured and structured for infrastructure monitoring, along with descriptions of each field used when creating and managing Metric configurations. Use this guide to understand how Metric configurations allow Namirasoft Infra to collect and structure operational data from various metric sources.

 

What Is a Metric?

A Metric in Namirasoft Infra represents a connection configuration that allows the platform to access, collect, and structure quantitative measurement data from monitoring endpoints. Metrics are numerical measurements that represent the performance, health, or behavior of your systems over time.

 

Metric configurations in Namirasoft Infra define how the platform connects to, schedules collection from, and processes data from metric endpoints. These configurations enable the collection of critical operational data including system performance indicators, application metrics, custom business measurements, and third-party monitoring data. This data is structured, normalized, and delivered to Namirasoft Expert, where it supports intelligent monitoring, trend analysis, anomaly detection, and automated remediation workflows.

 

Each Metric configuration belongs to a specific Project and Environment, ensuring that metric collection remains organized according to your operational context. Metric endpoints can be hosted in various environments (exposed via HTTP endpoints, accessed through servers, or collected from Kubernetes clusters) and Namirasoft Infra provides consistent metric collection through flexible caller methods.

 

The Challenge in Managing Metric Collection

Collecting and managing metrics from diverse sources presents significant operational challenges. As systems become more distributed and complex, maintaining reliable metric collection becomes increasingly difficult:

 

  • Endpoint Diversity: Different systems expose metrics in various formats (Prometheus, Graphite, custom JSON, etc.)

 

  • Collection Scheduling: Managing consistent collection intervals across hundreds of metric sources

 

  • Data Normalization: Converting diverse metric formats into a consistent structure for analysis

 

  • Access Complexity: Different authentication and access methods for various metric endpoints

 

  • Scale Management: Coordinating metric collection across thousands of endpoints without overwhelming systems

 

  • Data Quality: Ensuring metric reliability, consistency, and completeness

 

  • Integration Overhead: Manually integrating metrics from multiple sources into a unified monitoring system

 

While individual systems may provide metric endpoints, they typically lack centralized scheduling, normalization, and intelligent analysis capabilities.

How Namirasoft Infra Solves the Problem

Namirasoft Infra addresses metric collection challenges through structured Metric configurations that provide a standardized approach to collecting and processing measurement data from diverse sources.

 

Metric configurations establish a flexible framework for connecting to metric endpoints regardless of their format or location. By offering multiple caller types (global, via server, or via Kubernetes), Namirasoft Infra accommodates various access patterns while maintaining consistent collection capabilities across different metric sources.

 

Once configured, Namirasoft Infra automatically schedules metric collection based on your interval settings, normalizes the data into a consistent structure, and enriches it with contextual metadata. This processed metric data flows seamlessly to Namirasoft Expert, where it can be analyzed alongside other infrastructure and application data to provide comprehensive visibility into system behavior and performance trends.

 

By treating Metrics as first-class monitoring entities, Namirasoft Infra enables teams to maintain reliable metric collection, detect data quality issues, and leverage structured measurement data for proactive operational intelligence.

 

Overview of Metric Fields and Options

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

 

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

 

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

 

  • Workspace ID (Namirasoft Workspace’s ID): This refers to a workspace created in the Namirasoft Workspace app, which identifies the workspace where the Metric configuration is created. 

 

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

 

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

 

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

 

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

 

  • URL (String): This field specifies the endpoint where your system or application exposes its metric data. Namirasoft Infra needs this URL to periodically fetch (collect) metrics from that endpoint at the interval you define.

 

For detailed instructions on how to find or set up metric endpoints for different systems, see the Metric Endpoint Setup Guide.

 

  • Interval Scheduler (String): This field specifies which schedule from Namirasoft Scheduler determines how frequently metrics are collected from the URL. The selected schedule defines the exact interval (e.g., every 30 seconds, every 5 minutes, or every hour) at which Namirasoft Infra will fetch metric data.

 

You must create a schedule in Namirasoft Scheduler before selecting it here. If you haven’t created a schedule yet, click the “+” icon next to this field to open Namirasoft Scheduler and create a new one.

 

  • Caller Type (Enum): This field specifies how Namirasoft Infra will access the metric endpoint. The caller type determines what infrastructure component will execute the metric collection request.

 

 

    • Globally: Access the metric endpoint directly from Namirasoft Infra’s global infrastructure. Use this option when:

 

      • The metric endpoint is publicly accessible on the internet

 

      • Namirasoft Infra has direct network access to the endpoint

 

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

 

      • When you select “Globally,” metric collection requests originate from Namirasoft Infra’s global monitoring infrastructure.

 

    • By Server: Access the metric endpoint through a Server resource. Use this option when:

 

      • The metric endpoint is only accessible from within a specific network

 

      • You need to use a specific server as a proxy or gateway

 

      • The endpoint isn’t directly accessible from the public internet

 

      • When you select “By Server,” you will need to select which Server configuration to use. The Server must have network access to the metric endpoint and will execute the collection requests.

 

    • By Kubernetes: Access the metric endpoint through a Kubernetes cluster. Use this option when:

 

      • The metric endpoint is running inside a Kubernetes cluster

 

      • The endpoint is exposed as a Kubernetes service or pod

 

      • You need to access metrics from within the Kubernetes network

 

      • When you select “By Kubernetes,” you will need to select which Kubernetes configuration to use. The Kubernetes cluster will execute the metric collection requests from within its network.

 

  • Description (String): This field allows you to document the purpose, content, or special characteristics of the metric collection. It helps teams understand what metrics are being collected and their significance

 

  • Metric Credential ID (String): his is the unique identifier of the credential set used to access the metric endpoint. This references securely stored authentication information (API keys, tokens, certificates, etc.) without exposing the actual credentials. The system creates this automatically when you configure metric access credentials.

 

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

 

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

 

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

 

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

Keep Your Infrastructure Running Smoothly and Reliably

Get Started Now Explore Console Guide