Manage DX Cloud
The DX Cloud Cockpit is the control center for your Magnolia deployment. From the Cockpit, you can manage different aspects of your deployment.
- All users
-
-
Use and configure your whole DX Cloud project with Cockpit sections.
-
Manage your own user profile.
-
- Administrators
-
-
Manage your subscription’s users directly from the Cockpit.
-
Set your platform update preferences.
-
Platform Update tiers
Platform Update tiers are where you let us know how you want us to proceed with managing critical platform updates such as updates to infrastructure, Kubernetes, and other operational components for your DX Cloud project.
This is broken down into the following tiers:
| Tier | Description | Announce | Approval |
|---|---|---|---|
Tier 1 |
You do not require an announcement regarding updates, but we need approval to perform the updates. |
||
Tier 2 |
You would like an announcement made regarding updates, but we can perform the updates without explicit approval. |
||
Tier 3 |
You would like an announcement made regarding updates and the update window should be confirmed between both parties. |
Alerts
DX Cloud alerts provide a closer look at the status of your cluster(s). If there is an active alert, you’ll see a notification in the top of your Cockpit.
There are three categories of alerts:
Select desired cluster
Select your desired cluster from the dropdown menu at the top of the Cockpit.
Subscribe to alerts
You can subscribe to alerts through your user preferences.
| When an alert status changes (e.g., becomes active or inactive), you’ll receive 1 email for each alert update. |
Active alerts
As it sounds, active alerts are those alerts that are currently active for your cluster and should be seen to.
Pending alerts
Pending alerts means that at least one time series returned by the evaluation engine is Pending.
Inactive alerts
Inactive alerts are alerts that have already occurred. This is more for information purposes.
Alerts types
The following are the current alerts for DX Cloud.
| Alert | Description |
|---|---|
Magnolia container has been |
|
Magnolia instance has not been running for at least the last |
|
|
Magnolia service has application errors ( |
Magnolia author instance average response time for 90% of requests is more than 2 seconds for the last This also covers Magnolia public instance average response time for 90% of requests is more than 800 milliseconds for the last |
|
The node in a customer cluster is under heavy memory pressure. The available memory is under 5% and there is a high rate of major page faults. |
|
The filesystem on a <customer> cluster has less than 1% space available. |
|
The filesystem on a customer cluster has less than 30% space available and is projected to be full within |
|
A database persistent volume used by Magnolia on a customer cluster has less than 1% space available. You may not be able to successfully add or publish content to the Magnolia instance. |
|
A Magnolia home persistent volume on a <customer cluster> has less than 10% space available. You should try removing search indexes on the affected persistent volume to free up space. |
|
The certificate for a host/ingress on a customer cluster is expiring in |
|
Tomcat is using more than 20% of its thread pool for the last |
|
Magnolia instance is being restarted frequently by Kubernetes. |
|
The central backup server in your cluster is not running or not responding for at least |
|
A service running on your production cluster is returning errors (5xx) for more than 10% of requests for the last 10 minutes. |