--- title: Global rules slug: edgemanager/lem-administrator-guide/monitor-operations/alerts/global-rules docTags: createdAt: 2026-08-09T19:45:47.240Z --- Global Rules are a built-in set of platform-level alert rules that monitor the health of your Litmus Edge devices across every company and project. Unlike triggers, which you create one project at a time, Global Rules are maintained centrally and need no setup in individual projects. They give operations teams a consistent monitoring baseline. ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/-H20mWIR2r-9H1gTt3Bw7_image.png" size="80" isUploading="false" width="1918" height="864" darkWidth="1918" darkHeight="864" position="flex-start" showCaption="false"} ## Why global rules matter Managing many companies and projects makes it hard to keep monitoring consistent because a trigger added in one project does not exist in the others. With Global Rules: - One administrator manages a single set of rules that applies to every company and project. - New companies and projects inherit the rules automatically without any setup in individual project. - Common problems, such as offline gateways, low disk space, or expiring licenses, are detected in every project under the same conditions. Global Rules are aimed at platform administrators and operations teams who are responsible for edge devices across all projects rather than a single one. ## Global rule catalog The following global rules are available and enabled by default. | Rule | What it monitors | Type | | -------------------------- | --------------------------------------------------- | --------- | | Connector Status | Whether connectors are online | State | | DeviceHub Device Online | Whether DeviceHub devices are online | State | | Gateway Online Status | Whether edge gateways are online | State | | Marketplace App Lifecycle | When a Marketplace application stops or is restored | Event | | Gateway License Expiration | Licenses approaching expiry and expired licenses | Threshold | | Gateway Free Disk Space | Available disk space below a threshold | Threshold | | Gateway Memory Available | Available memory below a threshold | Threshold | | Gateway CPU Idle | CPU usage below a threshold | Threshold | ## What you can configure Settings vary by rule. Every rule has an enabled state, a severity, and an alert delay. The four gateway threshold rules also have a target value. You can override the default for individual rules. - **Enabled state**: Turn the rule on or off. - **Severity**: Set the incident severity to low, medium, or high. - **Target value**: Set a target value % threshold for disk space, memory, and CPU rules. Set a number of days threshold for the license expiration rule. - **Alert delay**: Set how long a condition must persist before Litmus Edge Manager (LEM) opens an incident. The delay is between 60 and 3,600 seconds. ## Rule scope A rule applies either to all projects or to a selected set. By default it applies to all projects, current and future, so a project created later inherits the rule without any action. You can instead scope a rule to specific projects, and only those projects raise incidents from it. The Projects column on the *Global Rules* list shows each rule's current scope. ## How global incidents work When a rule's condition is met for the length of its alert delay, LEM opens an incident in the project that owns the affected device. The incident is marked with a **Global** badge in the *Incidents* list so you can tell it apart from project-level incidents. Each affected project receives its own incident and sends notifications through that project's action templates. A problem in one project does not raise an incident in another project. When the condition clears, LEM resolves the incident automatically. A condition that stays active produces a single open incident for each device and rule rather than a stream of duplicates. License expiration is handled in tiers. LEM opens a separate incident for each threshold you configure and a further incident when a license has expired. ## Roles and permissions Only administrators can view and change global rules. A change to a rule takes effect across all companies and projects, so edits are limited to the admin role. User-defined project triggers are unaffected and continue to be managed within each project. ## Notification routing Each action template has a scope that controls which incidents it responds to: all incidents, global incidents only, or project incidents only. Global incidents are sent through templates scoped to all incidents or to global incidents only. Templates scoped to project incidents only are skipped for global incidents. An existing template with no scope set defaults to all incidents, so it continues to fire. ## Tracking and visibility You can track global incidents in two places: - The *Incidents* list in each project shows every global incident for that project marked with the **Global** badge. - Each rule has an audit timeline that records every change to the rule, including who made the change and the values before and after. ## Limitations and considerations - Global Rules includes a predefined set of rules. Set other rules to satisfy your needs in Project Settings. ## Access global rules To access Global Rules, in the Litmus Edge Manager Admin Console, go to **Alerts** > **Global Rules**. ## Related topics - [Incidents](docId\:vzRdFBVAkuIICMqOjOtrG) - [Set up alert triggers](docId\:VK_qMi8qjT6DrN74l2dj-)