Configuring event notifications
You can configure R‑Cloud to send notifications when new events occur in your data protection environment. This allows you to monitor and manage your data protection environment more efficiently, and to immediately respond to the events if required. You can set up emails or webhooks as a notification channel.
Important Make sure to configure event notifications for each protection set separately.

To access the Notifications dialog box, click Events in the navigation pane, and then click
Notifications in the toolbar.
Depending on which notification channel you want to use, see one of the following
Creating email notifications
Procedure
- In the Notifications dialog box, click the Email tab, and then click
New.
-
In the Subject field, enter a subject for the email notification.
-
From the Category drop-down menu, select one or more categories. To include all categories, click Select All. For a description of categories, see Viewing events.
-
From the Status drop-down menu, select one or more statuses. To include all statuses, click Select All. For a description of statuses, see Viewing events.
-
In the Email address field, enter the recipient's email address. If you are entering more than one email address, make sure to press the Spacebar after entering each one.
-
Click Save.
Your changes take effect immediately and email notifications are sent to any email address that you specified in the notification settings.
After you create a notification, you can do the following:
-
Edit the email notification settings by clicking
Edit.
-
Temporarily deactivate the email notification and stop sending emails by clicking
Deactivate. To resume sending emails, click
Activate.
-
Delete the email notification that you no longer need by clicking
Delete.
Creating webhook notifications
Procedure
-
In the Notifications dialog box, click the Webhooks tab, and then click
New.
-
Enter a name for the webhook notification and, optionally, its description.
-
From the Category drop-down menu, select one or more event categories. To include all categories, click Select All. For a description of categories, see Viewing events.
-
From the Status drop-down menu, select one or more statuses. To include all statuses, click Select All. For a description of statuses, see Viewing events.
-
In the Post URL field, enter the URL of the endpoint the webhook notifications should be sent to in one of the following formats:
https://<Host>
https://<Host>/<Path>
-
Only if the receiving endpoint requires sender's identification. From the Authentication type drop-down menu, select one of the following authentication types:
- Authentication by secret, and then enter the secret to connect to your webhook endpoint.
- Basic authentication, and then enter the user name and password associated with your webhook endpoint.
- Click Next.
-
Optional. Customize the body of the request that is sent by R‑Cloud. You can click the appropriate fields in the HYCU fields list to easily insert event variables into the body.
Important Make sure the format you define in the body is supported by the platform to which webhook notifications will be sent.
For details on the format of the data that R‑Cloud sends to the specified URL, see Configuring event notifications.
-
Click Save.
Your changes take effect immediately and webhook notifications are sent to any URL that you specified in the notification settings.
After you create a notification, you can do the following:
-
Edit the webhook notification settings by clicking
Edit.
-
Temporarily deactivate the webhook notification and stop sending the notifications by clicking
Deactivate. To resume sending the notifications, click
Activate.
-
Delete the obsolete webhook notification by clicking
Delete.
Webhook data format
The webhook data format is defined by:
- HTTP request header sent by R‑Cloud
- HTTP request body sent by R‑Cloud
-
HTTP response code sent by the webhook endpoint and received by R‑Cloud
HTTP request headers
The request headers are sent in the following format:
content-type = application/json
x-hycu-signature = base64(hmac(body, secret, 'sha256'))
Note The x-hycu-signature
request header is sent only if the webhook secret is specified.
HTTP request body
The request body is sent in the following format:
{
"severity": "<severityValue>",
"created": "<createdValue>",
"details": "<detailsValue>",
"category": "<categoryValue>",
"message": "<messageValue>",
"user": "<userValue>",
"taskId": "<taskIdValue>"
}
Note Null values are ignored.
HTTP response code
Your webhook URL should return a response with HTTP status code 204
.