Generator Low Oil Pressure Alarm

Who it’s for

Backup-generator operators, service engineers, and any team watching a low-reading metric asking “is this genset’s oil pressure dropping toward seizure?”, “is the diesel engine’s oil pump failing or is there a hidden oil leak?”, “is hydraulic line pressure, fuel level, or engine coolant slipping toward a low limit?” — when a low reading should trigger an early warning before it stays dangerously low long enough to escalate.

What it does

Reads the device’s oilPressure telemetry and raises a Major alarm when oil pressure drops below a safe level, escalating to Critical when it stays dangerously low long enough to risk engine damage. The alarm auto-clears once pressure recovers.

How to set up

The rule has default values for every threshold, so it works as soon as it is installed. Install on a device or asset profile so the alarm covers every entity of that type at once and automatically picks up any new entity added later. Single-device or single-asset installs are also supported.

How to customize

• To monitor a different telemetry — change the Time series key on the metric argument (e.g. oilPressure → batteryVoltage for low-battery monitoring, or fuelLevel for low-fuel monitoring).
• To use different threshold attribute names — change the Attribute key on the threshold arguments to match what your devices or assets already use (e.g. oilPressureWarningThreshold → oilPressureMin).
• To change the warning, danger, and clear thresholds used when no per-entity attribute is set — change the Default value on the warningThreshold, criticalThreshold, and clearThreshold arguments.
• To change how long the reading must stay at or below the danger threshold before Critical fires — change the Default value on the holdMinutes argument.
• To tune thresholds and hold duration at runtime without editing the rule — set the value on the entity as a regular server-side attribute. It can be edited directly from a dashboard using Update Multiple Attributes input widget:
  • Per device or asset — set the attribute (e.g. oilPressureWarningThreshold, oilPressureHoldMinutes) on the device or asset itself. The per-entity value overrides the Default value.
  • Per customer (in deployments that use customers) — change Entity type on the relevant argument to Current owner, then set the attribute on the customer. Every device that customer owns picks up that value.
  • Tenant-wide — change Entity type to Current tenant, then set the attribute on the tenant. The value applies across every device.
• To make the alarm manual-clear-only — remove the Clear condition. The alarm then stays active until an operator clears it.
• To restrict firing to specific hours or days — in the Trigger condition’s Schedule, choose Active at a specific time range (or Custom schedule for different intervals per day) — useful for suppressing alarms during planned shutdowns or scheduled maintenance windows. For per-entity schedules — gensets with different run schedules — switch to Dynamic mode and source the schedule JSON from an attribute on the entity.
• To control where the alarm shows up — toggle the propagation flags under Advanced settings.