TULPAR

Node Monitoring

Your Cluster's Pulse on One Screen

Instead of hopping between nodes over SSH, see the real state of your cluster instantly with Prometheus-based metrics, health checks and alerts.

SSH-free metric collection

Node agents stream metrics into Prometheus — scales naturally to 100+ nodes.

Observability built into the panel

Charts, alerts and logs inside the panel — without installing and maintaining Grafana.

TULPAR / Node Monitoring
Node Monitoring
Current TULPAR interface in Turkish · Sample test data

What's Inside

End-to-End Monitoring from Metric to Alert

From inventory to GPUs, from health checks to central logging — the whole monitoring stack ships with the installation.

01

Unified Inventory

Every node in one list: state, inline CPU/RAM summary, and a tabbed detail view.

02

Live Metrics

CPU, RAM, disk, network and InfiniBand time series — per node and cluster-wide.

03

GPU Monitoring

NVIDIA GPU inventory, utilization and temperature metrics via DCGM.

04

Health Checks

Service and node health probes, recorded automatically on the unified event timeline.

05

Alert Rules

Threshold-based rules; SMTP, webhook and in-panel notifications; silences and maintenance windows.

06

Central Logging

Node logs stream to the head over RELP+mTLS; search from the panel with LogsQL — 90-day retention.

TULPAR / Node Monitoring

From Inventory to Action

Watching isn't enough — TULPAR lets you act on what you see, from the same screen.

Prometheus architecture
Metrics flow from node_exporter and tulpar-agent into Prometheus; the panel reads via PromQL — none of the scaling limits of SSH-based collection.
Event timeline
Node, job and service events merge into one chronological stream, filterable by type and severity.
Alert lifecycle
Rule → firing → notification → ack; time-boxed silences and maintenance windows keep alert fatigue away.
Node actions
Drain, resume and reboot straight from the node detail view; the automation engine can bind the same actions to rules.
Node Monitoring
From Inventory to Action
Current TULPAR interface in Turkish · Sample test data

GOOD TO KNOW

Frequently Asked Questions

Got questions? Everything you need to know about installation, licensing and scaling is here.

How is TULPAR licensed?
TULPAR is an enterprise product offered under a commercial license. Licensing is annual, based on your cluster scale and the support coverage you need; every license includes the full feature set — there is no feature gating. Contact us through the contact page for a quote.
How long does installation take and what do I need?
An EL9-based head server is enough. tulpar-preflight.sh prepares the prerequisites, install.sh brings up the whole stack; you then enter the admin password, NTP, LDAP and SLURM settings in the web wizard. A typical installation completes in minutes.
Does it work with my existing Slurm cluster?
TULPAR talks to Slurm over the slurmrestd REST API and falls back to the CLI automatically, providing a stable, version-independent interface. Head Slurm components run natively on the host (dnf/systemd) and share the same repository and version as the compute nodes.
Can it be installed in an air-gapped environment without internet access?
Yes. RPM repositories travel with the product, the Slurm package repository can be imported as a GPG-signed offline bundle, and container images are loaded with docker load. Every component works on a closed network, including node installation, monitoring and central logging.

READY FOR YOUR NEXT COMPUTATION

Unleash your
infrastructure’s potential.

Let’s explore what TULPAR can do for your cluster.

Request a demo