Alerts

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

There are three categories of alerts:

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.
go to user preferences

Active alerts

As it sounds, active alerts are those alerts that are currently active for your cluster and should be seen to.

active alerts

Pending alerts

Pending alerts means that at least one time series returned by the evaluation engine is Pending.

pending alerts

Inactive alerts

Inactive alerts are alerts that have already occurred. This is more for information purposes.

inactive alerts

Alerts types

The following are the current alerts for Magnolia PaaS.

Alert Description

<Customer>MagnoliaContainerOomKilled

Magnolia container has been OOMKilled at least once in the last 10 minutes.

<Customer>MagnoliaDown

Magnolia instance has not been running for at least the last 30 minutes.

<Customer>MagnoliaServiceErrors

Magnolia service has application errors (503) for the last 5 minutes.

<Customer>MagnoliaAuthorSlowResponse

Magnolia author instance average response time for 90% of requests is more than 2 seconds for the last 15 minutes.

<Customer>MagnoliaPublicSlowResponse

Magnolia public instance average response time for 90% of requests is more than 800 milliseconds for the last 15 minutes

<Customer>ClusterHighMemoryPressure

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.

<Customer>ClusterFilesystemAlmostFull

The filesystem on a <customer> cluster has less than 1% space available.

<Customer>ClusterFilesystemFillingUp

The filesystem on a <customer> cluster has less than 30% space available and is projected to be full within 8 hours.

<Customer>DatabasePersistentVolumeFillingUp

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.

<Customer>DatabasePersistentVolumeFillingUp

A database persistent volume used by Magnolia on a <customer> cluster has less than 30% space available and is projected to be full within 8 hours. You may not be able to successfully add or publish content to the Magnolia instance.

<Customer>ArchivePersistentVolumeFillingUp

An archive persistent volume used by Magnolia on a <customer> cluster has less than 1% space available. You may not be able to make a Magnolia backup.

<Customer<ArchivePersistentVolumeFillingUp

An archive persistent volume used by Magnolia on a <customer> cluster has less than 30% space available and is projected to be full within 8 hours. You may not be able to make a Magnolia backup.

<Customer>MagnoliaHomePersistentVolumeAlmostFull

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.

<Customer>CertificateExpiring

The certificate for a host/ingress on a <customer> cluster is expiring in 14 days.

<Customer>TomcatHighLoad

Tomcat is using more than 20% of its thread pool for the last 10 minutes.

<Customer>MagnoliaCrashLooping

Magnolia pod is being restarted frequently by Kubernetes.

<Customer>MagnoliaFrontendCrashLooping

Magnolia front end pod is being restarted frequently by Kubernetes.

Feedback