Skip to content

Added note about Alarms count (deprecated) node #559

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vvlladd28 merged 1 commit into from
Jul 20, 2026
Merged

Added note about Alarms count (deprecated) node #559

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions src/content/_includes/docs/reference/rule-engine/nodes/analytics/alarms-count.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,10 @@ import { Aside } from '@astrojs/starlight/components';

Use this node to count alarms matching configured criteria and write the count as telemetry — for example, maintaining a real-time `activeAlarmCount` metric on a device asset that increments when new alarms are created and decrements when they are cleared, or tracking how many critical alarms occurred in the last 24 hours.

<Aside type="note">
An older *alarms count (deprecated)* node is still available for legacy rule chains. Instead of reacting to incoming messages, it runs on a fixed schedule and counts alarms for a statically configured target — a single entity, an entity group, or a relations query — rather than resolving the originator dynamically. Use the node described here for new rule chains.
</Aside>

## Configuration

- **Count alarms for propagation entities** — when enabled, counts alarms not only for the message originator but also for all entities to which those alarms are propagated.
Expand Down