Cloud
Alerting and Events
Overview

Alerting Overview

AERL Cloud's alerting system provides proactive monitoring and instant notifications for critical events across your energy infrastructure.

How Alerting Works

Alert Flow

  1. Monitoring: Continuous evaluation of device metrics
  2. Detection: Alert rules trigger when conditions are met
  3. Creation: Alert is generated with context and severity
  4. Notification: Email sent to configured receivers
  5. Response: Team acknowledges and resolves issue
  6. Resolution: Alert remains as historical record even when condition returns to normal

Key Components

  • Alert Rules: Define what conditions trigger alerts
  • Active Alerts: Current issues requiring attention
  • Receivers: Who gets notified when alerts fire
  • Acknowledgment: Track who responded to alerts
  • History: Complete audit trail of all alerts

Alert Concepts

Severity Levels

Every alert has one of three severity levels:

Information

  • Normal operational events
  • Status changes worth noting
  • No immediate action required
  • Examples:
    • Device came online
    • Maintenance mode activated
    • Daily report generated

Warning

  • Potential issues developing
  • Preventive action recommended
  • Not yet critical
  • Examples:
    • Battery SOC below 30%
    • Temperature approaching limit
    • Communication intermittent

Error

  • Critical failures detected
  • Immediate attention required
  • System functionality impaired
  • Examples:
    • Device offline
    • Battery critical low
    • Inverter fault detected

Alert States

Active

  • Condition currently true
  • Requires acknowledgment
  • Shows in active alerts list
  • Notifications being sent

Acknowledged

  • Team member responded
  • Issue being addressed
  • Tracks who acknowledged
  • Prevents duplicate notifications

Historical Record

  • Alerts remain in system permanently
  • Provides audit trail of all events
  • Condition status tracked over time
  • Manual acknowledgment tracked

Alert Dashboard

Navigation

Access alerts from:

  • Main menu → Alerts
  • Dashboard alert counters
  • Navbar notification bell

Alert Views

Active Alerts Tab

Shows all unresolved alerts:

  • Time triggered
  • Location affected
  • Severity indicator
  • Alert details
  • Notification status
  • Acknowledge button

Alert Rules Tab

Manage alert configurations:

  • Rule name and description
  • Query expression
  • Severity setting
  • Duration threshold
  • Edit/delete actions

Receivers Tab

Configure notifications:

  • Email addresses
  • Severity filters
  • Add/edit/remove

Filtering and Search

  • Severity Filter: Show specific levels
  • Time Range: Last hour/day/week
  • Search: Find by location or alert name
  • Location Filter: Alerts from specific sites

Understanding Alert Data

Alert Information

Each alert displays:

  • Time: When condition triggered
  • Location: Affected site name
  • Severity: Visual indicator and text
  • Details: Alert rule name and description
  • Notified: Email delivery status
  • Actions: Acknowledge or view details

Metadata

Additional context includes:

  • Device/gateway affected
  • Metric values that triggered
  • Duration of condition
  • Previous occurrences

Alert Counts

Summary Cards

Dashboard shows:

  • Active Alerts: Total unacknowledged
  • By Severity: Breakdown by level
  • Acknowledged Today: Response metrics
  • Alert Rules: Total configured
  • Receivers: Email count

Real-Time Updates

  • Counts refresh automatically
  • New alerts appear instantly
  • Navbar badge shows total
  • Color coding by severity

Acknowledgment Process

Why Acknowledge?

  • Indicates someone is responding
  • Prevents alert fatigue
  • Tracks response times
  • Creates accountability

How to Acknowledge

  1. Click check icon on alert
  2. Or use "Acknowledge All"
  3. Your name and time recorded
  4. Alert remains visible but marked

Who Can Acknowledge?

  • Owners
  • Admins
  • Technicians
  • (Viewers cannot acknowledge)

Email Notifications

Delivery Status

  • Pending: Queued for sending
  • Sending: In progress
  • Sent: Successfully delivered
  • Failed: Delivery error

Email Content

Notifications include:

  • Alert severity and name
  • Location affected
  • Time triggered
  • Direct link to alert
  • Metric details

Delivery Rules

  • Sent to all configured receivers
  • Filtered by severity preferences
  • Retry on failure
  • Rate limited to prevent spam

Best Practices

Alert Design

  • Specific Conditions: Avoid overly broad rules
  • Appropriate Severity: Match importance
  • Clear Names: Descriptive alert titles
  • Actionable: Include what to do

Noise Reduction

  • Set appropriate thresholds
  • Use duration requirements
  • Configure severity filters
  • Regular rule review

Response Procedures

  • Document response steps
  • Assign on-call schedules
  • Track resolution times
  • Review recurring issues

Common Alert Scenarios

Equipment Monitoring

Battery voltage < 11.5V for 5 minutes
Device offline for 10 minutes
Inverter temperature > 65°C
Generator fuel < 20%

Performance Alerts

Solar production < 100W during daylight
Battery not charging for 2 hours
Load exceeding inverter capacity
Low system efficiency

Maintenance Reminders

Service interval reached
Calibration due
Filter replacement needed
Firmware update available

Integration Options

Webhook Support

Coming soon:

  • Send to external systems
  • Custom JSON payloads
  • Integration with:
    • Slack
    • Microsoft Teams
    • PagerDuty
    • Custom webhooks

API Access

  • Query alerts programmatically
  • Acknowledge via API
  • Create custom dashboards
  • Build integrations

Troubleshooting

Not Receiving Emails

  • Check receiver configuration
  • Verify email address
  • Check spam folder
  • Review severity filter

Too Many Alerts

  • Adjust thresholds
  • Increase duration
  • Review rule logic
  • Disable noisy rules

Alerts Not Clearing

  • Verify condition resolved
  • Check rule logic
  • Manual acknowledgment
  • Contact support

Next Steps

ServiceConfiguring Triggers