> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/foodcore-sensors/admin/alerts-and-actions/notifications.md).
# Notifications
#### Purpose
The Notifications Log is a key feature within the system that maintains a full audit trail of all alert communications sent from the platform. It supports traceability, accountability, and dispute resolution, by recording every notification that is triggered by temperature breaches, sensor anomalies, or other rule-based thresholds.
***
Overview
The log presents a detailed list of notifications that have been automatically triggered and sent to users. This includes those tied to:
* Temperature threshold breaches
* Sensor errors or invalid readings
* Triggered corrective actions
It allows users and administrators to verify the messages sent, check the timing, and ensure the alert system is functioning as expected.
***
#### Key Fields
| Column | Description |
| ---------- | ------------------------------------------------------------------------------------------------------------- |
| # | Sequence number of the notification in the log. |
| Capability | Type of data the alert was based on, e.g., temperatureC\_SHT or temperatureC\_TMP117. |
| Sent At | The exact date and time the notification was issued. |
| Levels | Priority or escalation level of the notification (e.g., \[1]). |
| Status | Status of the alert delivery, typically marked as SENT. |
| Message | Full text of the alert, including device name, sensor reading, threshold data, and prior values if available. |
***
#### Example Notification Entry
Message:
Device CR1-MNK-FR1 (IRD) (89) Walk In Freezer has high Ambient -1.01°C. Alarm Threshold Set -5°C. Prev Histories: 1) -1.01°C | 2) -16.97°C | 3) -16.92°C | 4) -16.34°C | 5) -15.76°C | 6) -15.24°C
This provides:
* Device label for identification
* Type of issue (e.g., high ambient temperature)
* Thresholds and historical values leading to the alarm
***
#### Features
* Complete Audit Trail: Every alert is documented with a timestamp and delivery status.
* Verifiable Delivery: Confirms whether alerts were successfully sent.
* Message Transparency: View exact message content sent via Email, WhatsApp, or other platforms.
* Compliance Tool: Useful for audits or inspections requiring proof of notification.
* Corrective Action Linkage: Ties notifications to corresponding corrective actions where applicable.
***
#### Use Cases
* Audit Readiness: Demonstrates proper functioning of your monitoring and alerting system.
* User Disputes: Resolves disagreements around whether notifications were sent.
* System Monitoring: Ensures alert rules are triggering as expected and within defined thresholds.
* Post-Incident Reviews: Understand the chain of events and data at the time of a temperature breach or equipment failure.
***
The Notifications Log is a foundational feature in your compliance and alerting workflow, enabling confidence, accountability, and transparency across the system.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.didge.io/home/foodcore-sensors/admin/alerts-and-actions/notifications.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
