DuploCloud allows automatic generation of alerts for resources within a Tenant. This makes sure that the defined baseline of monitoring is applied to all current and new resources based on a set of rules.

As an Administrator:

1. From the DuploCloud Portal, navigate to Administrator -> Tenants.

2. Click the name of your Tenant from the list and select the Alerting tab.

3. Click Enable Alerting. An alerts template displays. The alerts template contains rules for each AWS namespace and metric to be monitored.

4. Review the alerts template, and adjust the thresholds

5. Click Update

You can configure Hosts to auto-reboot and heal faults automatically, either at the Tenant level, or the Host level. See the Configure Auto Reboot topic for more information.

Introduction

Faults that happen in the system, be it Infrastructure creation, container deployments, Application health checks, or any Triggered Alarms can be tracked in the DuploCloud portal under Faults Menu.

Viewing Faults

You can look at Tenant-specific faults under Observability -> Faults or all the faults in the system under Administrator -> Faults.

Creating Alerts

You can set the AWS Alerts for individual metrics.

1. From the DuploCloud portal, navigate to Observability -> Alerts and click Add. The Create Alert pane displays.

2. Enter the Resource Type and select the resource from the Resource type list box. Click Next.

3. Fill in the necessary information and click Create. The Alert is created.

Viewing Alerts

• View general alerts from the DuploCloud Portal in the Observability -> Alerts.

• Select the Alerts tab for alerts pertaining to a specific resource, such as Hosts.

DuploCloud supports viewing of Faults in the portal and sending notifications and emails to the following systems:

• Sentry

• PagerDuty

• NewRelic

• OpsGenie

You will need to generate an keys from each of these vendor systems, and then provide that key to DuploCloud to enable integration.

Generating an Integration Key from Sentry

1. In the Sentry website, navigate to Projects -> Create a New Project.

2. Click Settings -> Projects -> project-name -> Client keys. The Client Keys page displays.

3. Complete the DSN fields on the screen.

4. Click Generate New Key.
5. In the DuploCloud Portal, navigate to Observability -> Faults.

6. Click Update Notifications Config. The Set Alert Notifications Config pane displays.

7. In the Sentry - DSN field, enter the key you received from Sentry.

8. In the Alerts Frequency (Seconds) field, enter a time interval in seconds when you want alerts to be displayed.

9. Click Update.

Generating an Integration Routing Key from PagerDuty

1. In the PagerDuty website home page, select the Services tab and navigate to the service that receives Events. If a Service does not exist, click New Service. When prompted, enter a friendly Name (for example, your DuploCloud Tenant name) and click Next.

2. Assign an Escalation policy, or use an existing policy.

3. Click Integration.

4. Click Events API V2. Your generated Integration Key is displayed as the second item on the right side of the page. This is the Routing Key you will supply to DuploCloud.

5. Copy the Integration Key to your Clipboard.

6. In the DuploCloud Portal, navigate to Observability -> Faults.

7. Click Update Notifications Config. The Set Alert Notifications Config pane displays.

8. In the Pager Duty - Routing Key field, enter the key you generated from PagerDuty.

9. In the Alerts Frequency (Seconds) field, enter a time interval in seconds when you want alerts to be displayed.

10. Click Update.

Generating an Integration Key from NewRelic

1. In the NewRelic website, use the Event API to generate an API key to send events to NewRelic Insights.

2. In the DuploCloud Portal, navigate to Observability -> Faults.

3. Click Update Notifications Config. The Set Alert Notifications Config pane displays.

4. In the NewRelic - API Key field, enter the key you generated from NewRelic.

5. In the Alerts Frequency (Seconds) field, enter a time interval in seconds when you want alerts to be displayed.

6. Click Update.

OpsGenie

1. In the OpsGenie website, generate an API Key to integrate DuploCloud faults with OpsGenie.

2. In the DuploCloud Portal, navigate to Observability -> Faults.

3. Click Update Notifications Config. The Set Alert Notifications Config pane displays.

4. In the OpsGenie - API Key field, enter the key you generated from OpsGenie.

5. In the Alerts Frequency (Seconds) field, enter a time interval in seconds when you want alerts to be displayed.

6. Click Update.

SNS Topic Alerts provide a flexible and scalable means of sending notifications and alerts across different AWS services and external endpoints, allowing you to stay informed about important events and incidents happening in your AWS environment.

SNS is a fully managed service that enables you to publish messages to topics. The messages can be delivered to subscribers or endpoints, such as email, SMS, mobile push notifications, or even HTTP endpoints.

Configuring this setting will attach the SNS Topic to the alerts in the OK and Alarm state.

Configuring Tenants to set SNS Topic Alerts

1. In the DuploCloud Portal, navigate to Administrator -> Tenants. The Tenants page displays.

2. Select the Tenant for which you want to set SNS Topic Alerts from the NAME column.

3. Click the Settings tab.

4. Click Add. The Add Tenant Feature pane displays.

5. From the Select Feature list box, select Set SNS Topic Alerts.

6. In the field below the Select Feature list box, enter a valid SNS Topic ARN.

7. Click Add. The configuration is displayed in the Settings tab.

Disabling faults for Target Groups without instances

If there is a Target Group with no instances/targets, DuploCloud generates a fault. You can configure DuploCloud's Systems Settings to ignore Target Groups with no instances.

1. From the DuploCloud portal, navigate to Administrator -> Systems Settings.

2. Select the System Config tab.

3. Click Add. The Add Config pane displays.

4. For ConfigType, select Other.

5. In the Other Config Type field, type Flags.

6. In the Key field, enter IgnoreTargetGroupWithNoInstances.

7. In the Value field, enter True.

1. Click Submit. The Flag is set and DuploCloud will not generate faults for Target Groups without instances.