Rule-Based Alerts
Define rules on metric thresholds, health checks or event types; a useful default rule set ships with the panel.
TULPAR
Alerting & Incident Management
See the Problem Before Your Users Do
Rule-based alerts watch metric thresholds and health events; when one fires it reaches you by email, webhook and in-panel notification — with silences and maintenance windows to match.
One flow from rule to notification
Threshold → firing → notification → acknowledgement; the whole chain is followed on one screen.
Noise control
A time-boxed silence suppresses only the notification; the alert keeps evaluating normally in the background.
What's Inside
The Full Alerting Loop
From defining a rule to reviewing incident history, every step happens in the panel.
Multi-Channel Notification
Email (SMTP), webhook and in-panel notification; channel settings are managed in the panel and secrets come back masked.
Silences & Maintenance
Define a time-boxed silence for planned maintenance; when the window ends the silence lifts itself.
Acknowledgement
Take ownership of a firing alert; who acknowledged it and when is recorded.
Channel Testing
Send a test notification before a channel goes live — no surprise webhook failures at the critical moment.
Event Timeline
Alerts, health events and system events converge into one stream, making retrospectives straightforward.
TULPAR / Alerting & Incident Management
From Alert to Action
The alerting engine doesn't just inform you — it is the signal source for the automation engine.
Signals into automation
Firing alerts land in an event pool; automation rules read that pool to trigger drain, reboot and power actions.
Undo a rule change
Restore a modified default rule to its factory value in one click, and bring back one you hid.
Secrets stay masked
SMTP passwords and webhook tokens are masked in API responses; the panel never returns a secret in clear text.
Nightly watchdog integration
The nightly drift, surface and backup-freshness checks write their findings into the panel's own event stream — no separate monitoring system to stand up.
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