Rule Logs Overview

A guide on understanding, debugging, and auditing your automation rules

Rule Engine Logs provide full visibility into how your automations behave on Datacake. Every time a rule is evaluated or executed, Datacake records a detailed log entry. This gives you a transparent audit trail that is especially helpful for debugging, monitoring large fleets, and meeting compliance requirements.

---

Where to find Rule Logs

Rule Logs are available to those who have access to the Advanced Rule Engine. This comes as a feature in our Standard, Plus, and Enterprise subscription plans (more details can be found on our Pricing page). Please reach out to [email protected] to enable the feature.

1. Open the Rule Engine

Navigate to: Workspace → Rule Engine → Logs as shown below.

2. Select a Rule

Each rule entry offers an option to open its log history.

3. Inspect Log Details

Inside a log entry you can:

• Expand the trigger information

• Inspect each executed action

• Check communication results (emails, webhooks, downlinks)

• See the conditions that were or were not fulfilled

4. Use Filtering & Search

Depending on your workspace size, logs can grow quickly. The UI lets you filter by:

• Time Frame

• Device

• An action that has been executed more than once (toggle switch)

---

What’s Included in a Log Entry

Each log entry captures several categories of information:

Rule Metadata

• Rule name

• Product or device the rule applied to

• Time of action

• Whether it was executed or not (in the form of a check or cross symbol)

Actions Executed

For each action, the log shows:

• Whether the action ran successfully

• Any returned data or diagnostics

This is particularly helpful when troubleshooting integrations.

Execution & System Info

Additional metadata includes:

• Evaluation timestamp

• Any warnings or error messages

• Information about skipped actions (e.g. “Action Not Executed”)

---

Example Use Cases

Debugging an Alert Rule

You can quickly see:

• Which measurement triggered the rule

• Whether the condition evaluated correctly

• Why an alert email was sent (or not sent)

Auditing Device Behavior

For compliance-heavy environments, you can track:

• When devices reported certain values

• When automated actions (like downlinks) were sent

• The exact data used during rule evaluation

Troubleshooting Scheduled Jobs

If a task did not run, logs allow you to determine:

• Whether the schedule was evaluated

• Whether execution was skipped