Dashboard Overview

The primary interface of INFINI Console serves as a centralized command center for monitoring and administrative tasks. The top navigation bar displays real-time counters for active alerts, system notifications, and pending operational tasks. The central pane aggregates critical infrastructure metrics, typically presenting the total number of managed clusters, active nodes, underlying hosts, and aggregated storage consumption.

Beneath the overview metrics, quick-action widgets provide direct access to frequently used workflows, including new cluster registration, advanced data exploration, alert configuraton, and security policy management. A side panel tracks recent system events, logging timestamped activities such as index creation, state transitions, and configuration updates across registered environments.

Cluster & Resource Management

The management interface organizes infrastructure data through tabbed navigation covering Clusters, Nodes, Indices, and Hosts. Each tab presents a detailed data grid containing performance and configuration metrics. For clusters, administrators can monitor health trends over a rolling window, track node and index counts, analyze shard distribution, and observe real-time indexing and query throughput alongside disk and JVM heap utilization.

Advanced filtering and sorting capabilities allow operators to narrow down resources by health status, engine distribution (e.g., Easysearch vs. Elasticsearch), software version, geographic region, or custom metadata tags. These filtering mechanisms apply consistently across node, index, and host views, enabling granular inspection of CPU load, memory allocation, disk I/O, and network throughput for individual components.

Performance Metrics & Reporting

The monitoring dashboard offers time-series visualization for cluster health and operational performance. Users can adjust the observation window (e.g., 15 minutes, 1 hour, 24 hours) and manually refresh data streams. The overview section displays foundational attributes such as cluster uptime, software version, health status, shard allocation ratios, unassigned shards, total document count, and storage/JVM consumption.

Performance charts break down system behavior into key operational dimensions:

• Indexing Throughput: Total and primary shard indexing rates (documents per second).
• Query Throughput: Overall search request volume.
• Latency Metrics: Time delays for indexing, deletion, query execution, result fetching, and scroll operations.

Expanding the advanced metrics view reveals node-level diagnostics (CPU saturation, system load, disk availability, process uptime) and index-level analytics (status distribution, shard configuration, storage footprint per index). This layered approach enables precise bottleneck identification and capacity planning.

Index Aliases & Rollover Strategies

Index aliases provide a logical mapping layer that decouples application queries from physical index names. Console supports both programmatic API calls and a graphical interface for managing these mappings. Below is a example of atomically adding a filtered alias while removing an outdated one:

POST /_aliases
{
  "actions": [
    {
      "add": {
        "index": "logs_production_2024",
        "alias": "active_logs",
        "filter": { "term": { "status": "active" } },
        "routing": "prod"
      }
    },
    {
      "remove": {
        "index": "logs_staging_old",
        "alias": "active_logs"
      }
    }
  ]
}

For time-series or high-volume data, index rollover automates lifecycle transitions. When a write index satisfies predefined thresholds, the system creates a successor index and atomically redirects the write alias. The following request demonstrates a rollover trigger based on shard size and index age:

POST /metrics_write_alias/_rollover
{
  "conditions": {
    "max_primary_shard_size": "50gb",
    "max_index_age": "30d"
  },
  "settings": {
    "number_of_replicas": 1,
    "index.lifecycle.name": "metrics_retention_policy"
  }
}

The console's visual creator simplifies this process by allowing administrators to define alias targets, routing keys, search filters, and rollover conditions through form-based inputs, eliminating manual DSL construction for routine tasks.

Platform-Wide Monitoring & Alerting

Beyond individual cluster metrics, the platform aggregates environmental telemetry. Dashboards illustrate engine adoption ratios, cloud provider distribution, underlying JDK versions, and resource consumption rankings. Top disk and JVM utilization charts highlight infrastructure nodes requiring immediate attention or rebalancing.

The alerting engine supports custom rule definitions mapped to specific metric thresholds. Operators can configure severity tiers and attach notification channels directly within the console. Supported delivery mechanisms include Discord, Lark (Feishu), WeChat, Slack, DingTalk, SMTP email servers, and generic webhook endpoints. Each channel requires minimal configuration, often limited to API tokens or webhook URLs, ensuring rapid integration with existing ITSM or DevOps pipelines.

Data Explorer & Development Tools

The integrated data explorer functions as a query interface for ad-hoc analysis, supporting time-range filtering, field-level drilling, and result visualization across indices and composite views. It mirrors the discovery experience of traditional log analysis tools while maintaining compatibility with Console's authentication and multi-cluster routing.

The development workspace extends standard DSL execution with multi-tab cluster routing, pre-built query templates, and native SQL translation capabilities. This environment streamlines iterative testing, schema validation, and performance tuning without leaving the management interface.

Security, Credentials & Audit Trails

Infrastructure access is governed through a centralized credential vault that tracks authentication tokens, certificates, and connection states for all registered clusters. Status indicators immediately flag expired or misconfigured credentials.

Administrative controls include user provisioning, role-based access assignments, and password rotation for the management interface. Concurrently, an immutable audit log captures all administrative actions, from metric queries to index modifications, providing compliance-ready traceability and facilitating post-incident investigations.