Orphaned environment reporting

Orphaned environments are environments that have been deleted from the Heropa platform but the deletion in the cloud provider has failed. This article provides guidance on configuring and managing orphaned environment reports for customers using BYO Azure accounts and BYO AWS accounts.

Detection

Heropa detects orphaned environments every 12 hours. If an orphaned environment is found, Heropa will attempt to delete it once every hours for up to three hours (three attempts). If all three attempts fail, the environment is marked as 'delete failed'.

Email notification

An email notification can be configured to be sent out once every 24 hours. The email notification will report all orphaned environments that have been detected and have not been resolved.

To configure the Orphan Environments email notifications:

1. From the left navigation menu, select Administration / Email templates
2. Select the Orphan Environments email template and then click on the Recipients tab.
3. Select which groups will receive the email notification by moving them from the Available groups box on the left hand side, to the Notified groups box on the right hand side.

Optionally: you can modify the branding and format of the email template from the HTML tab

Viewing orphaned environments

To view the list of orphaned environments for your company:

In the left hand navigation menu, select Administration, then select Orphans.

Managing orphaned environments

From the list of orphaned environments, you can perform the following actions via the row actions or bulk actions:

1. Start/Stop the environment;

2. Mark as manually deleted;

3. Delete environment: This will trigger another deletion attempt by Heropa.

Investigating orphaned environments

For detailed information on an orphaned environment:

1. Click on the orphaned environment to open the Environment Details page.

2. In the Logs tab, view logs of the failed destroy attempts, including any error messages explaining why the deletion failed.

Note: All configuration settings within an orphaned environment will be read-only.