Understanding Alerts

What are Alerts

Alerts are notifications generated by Project Green when something in your monitored environment requires attention. They are the primary way the platform communicates that a device has gone offline, a room is experiencing issues, or a threshold you configured has been exceeded. Alerts help you stay proactive rather than reactive.

Each alert contains key information including what triggered it, when it occurred, which room or device is affected, and the severity level. This context helps you quickly understand the situation and decide on the appropriate response without needing to investigate from scratch.

Alerts can be generated automatically based on the monitoring data collected by agents, or they can be tied to specific rules and thresholds that you or your administrator have configured. The goal is to ensure that the right people are informed about the right issues at the right time.

Alert Severity Levels

Alerts in Project Green are categorized by severity to help you prioritize your response. The most common levels are Critical, Warning, and Informational. Each level indicates how urgently the issue needs to be addressed.

Critical alerts indicate a serious problem that is likely affecting users right now, such as a primary display being completely offline or a control system being unreachable. These should be investigated and resolved as quickly as possible. Warning alerts signal a potential issue that may become critical if left unaddressed, such as intermittent connectivity or a device running outside normal parameters.

Informational alerts are low-priority notifications that provide useful context but do not require immediate action. These might include a scheduled maintenance window starting, a device reboot completing successfully, or a room entering a planned offline state. Understanding these severity levels helps you focus your energy on the issues that matter most.

Viewing Active Alerts

The Alerts section of the platform provides a comprehensive view of all active alerts across your environment. You can access it from the navigation sidebar. The list can be filtered by severity, location, device type, or time range, making it easy to find the specific alerts you are looking for.

Each alert in the list shows a summary line with the severity indicator, the affected room or device, and the time the alert was triggered. Clicking on an alert opens a detail view with the full context, including the specific condition that triggered it, any related historical data, and recommended next steps.

You can also view alerts directly from the dashboard widgets or from within a specific room's detail page. This means you do not always need to go to the central alerts section. Wherever you are in the platform, relevant alerts are surfaced to keep you informed.

Acknowledging and Resolving Alerts

When you see an alert that you are going to investigate or that you have already handled, you can acknowledge it. Acknowledging an alert signals to your team that someone is aware of the issue and is taking action. It does not close the alert but changes its status so others know it is being handled.

Once the underlying issue is resolved, the alert can be marked as resolved. In many cases, the platform will automatically resolve an alert when the condition that triggered it returns to normal. For example, if an alert was raised because a device went offline, it will typically auto-resolve once the device comes back online.

Keeping your alert list tidy by acknowledging and resolving alerts promptly is a good practice. It helps your entire team understand the current state of your environment and ensures that new, genuine issues stand out rather than getting lost in a backlog of stale alerts.

Setting Up Notifications

By default, alerts appear in the platform interface, but you can also configure notifications to be sent to you via email or other channels. This ensures you are informed about important issues even when you are not actively looking at the dashboard.

Notification settings can be configured at the account level and, in some cases, at the alert rule level. You might choose to receive email notifications only for critical alerts while viewing warnings and informational alerts in the platform. This layered approach helps prevent notification fatigue.

If your organization uses team communication tools, ask your administrator about integration options. Some setups allow alerts to be sent to shared channels, ensuring that the on-call team or the relevant support group is always in the loop. The key is to match your notification setup to your team's workflow and response process.