Manage alerts and integrations

The Local WEKA Home can be configured to send alerts through Email (SMTP), PagerDuty, SNMP Traps (v1/v2c/v3), and Syslog (RFC 5424). For instance, you can set it to send email notifications to a specific address if the cluster's data protection level drops below a set threshold.

WEKA Home email alert example

Set the Local WEKA Home to send events and alerts

Setting the Local WEKA Home to send events and alerts includes the following procedures:

1. Create an integration: Set the destination on the Integration page.

2. Create rules: On the Rules page, select the rule conditions to trigger specific alerts or events and assign the rule to the integration.

Create an integration

1. Access the Local WEKA Home portal with an admin account and the password (obtained during the LWH deployment. For example, see Deploy Local WEKA Home on K3s).

2. From the menu, select Manage > Integrations.

3. On the Integration page, select New.

Integrations page

1. On the Create Integration page, select one of the destinations and set the relevant values as follows:

PagerDuty

1. In Name, enter a meaningful destination name for the integration.

2. In Type, select PageDuty.

3. In Routing Key, set the routing key of your pager duty.

4. Ensure the integration is enabled (indicated by a green arrow).

5. Select Save Integration.

PagerDuty integration

Email

SNMP Trap

Syslog

Syslog technical reference

After configuring the Syslog integration, use the following technical details to ensure your Syslog server or SIEM (such as, Splunk, LogRhythm) can correctly parse the incoming data.

Message format

Local WEKA Home messages follow the RFC 5424 standard:

<PRI>1 TIMESTAMP HOSTNAME weka-home - MSGID [STRUCTURED-DATA] MESSAGE

• PRI: Calculated from facility (User = 1) and WEKA severity.

• TIMESTAMP: ISO 8601 / RFC 3339 format (example, 2026-03-05T12:39:51Z).

• HOSTNAME: Node ID (if available), cluster name, or weka-home.

• APP-NAME: Always weka-home.

• MSGID: The event or alert type (spaces are replaced with underscores).

• STRUCTURED-DATA: Key-value pairs in RFC 5424 format: [params key="value" ...].

• MESSAGE: The human-readable description of the notification.

Payload contents

The structured data/JSON payload varies by notification type:

• Events: customer_name, event_type, cluster_id, event_fields, severity, weka_home_url

• Alerts: customer_name, alert_type, cluster_id, title, content, action, severity, weka_home_url

Severity mapping

WEKA severity levels are mapped to standard Syslog severity codes:

WEKA severity	Syslog severity	Code
Critical	CRIT	2
Major	ERR	3
Minor / Warning	WARNING	4
Info	INFO	6
Debug	DEBUG	7
None (default)	NOTICE	5

Connection settings

Connection timeout: 10 seconds for all protocols (UDP, TCP, and TLS).

Create a rule

1. From the menu, select Manage > Rules.

2. On the Rules page, select New.

Rules page

1. On the Create Rule page, do the following:

   1. Enter a meaningful name for the rule.

   2. Select the event or alert type from Rule Type and set the entity, operator, and condition, for the selected rule type.

   3. Select View integrations and select the required integration (destination) from the list.

   4. Select Save Rule.

   A green confirmation message appears for a successful setting.

Examples

Create an event rule that sends all critical events to a predefined email

Create an event rule example

Create an alert rule that sends all tiering connectivity alerts to a predefined email

Create an alert rule example