Managing Magnolia PaaS

Your Magnolia PaaS Environments section contains critical information about your deployment’s health, response times, and overall usage.

Magnolia PaaS runs on Kubernetes clusters. Kubernetes clusters are sets of node machines running containerized applications. One of the primary advantages of Kubernetes clusters is that they automatically manage your cluster to match the configured desired state.

For more on cache in general for Magnolia PaaS, see here. Content Delivery Networks (CDNs) allow you to quickly deliver your site content by caching content appropriately for improved speed and performance. Magnolia PaaS uses Fastly as the default CDN. If you’re using Fastly as your CDN, you’ll be able to see all available tabs in the Cockpit.

Your Magnolia PaaS Logs section in the Cockpit displays logs for pods, domains, and ingresses. Each tab has dedicated filtering by their relevant components as well as by a date range.

Your Magnolia PaaS Dev operations section allows you to restore, copy, or download your project’s content database(s). You can also perform full backups in this part of the Cockpit.

The Audit section allows you to see the different actions being triggered by your team while they navigate and use the Cockpit. This ranges from things like user log-ins to those performing backup and restore options.

The Admin section of the Cockpit allows you to perform administrative operations on your subscription such as flushing individual (or all) query caches.

Your Magnolia PaaS Reports section contains important information about your deployment’s SLAs.

Magnolia PaaS alerts provide a closer look at the status of your cluster.