Simplified and Cost-Efficient GKE Node Management with NAP:
Secure your spot!
LogoLogo
PerfectScale.ioStart for FreeYour Account
  • Kubernetes Optimization
  • Getting started
    • How to onboard a cluster
    • Onboarding clusters programmatically
    • Onboarding with ArgoCD
    • Updating PerfectScale Agent resources
    • Re-onboarding a cluster
  • Enable automation
    • Automation setup instruction
    • Including a cluster, namespace or workload to the Automation
      • Configuring Automation for a cluster
      • Configuring Automation for a namespace
      • Configuring Automation for a workload
    • Excluding a namespace or workload from the Automation
    • Automation customization
    • Verifying Automation status
    • Exploring Automation KPIs
    • Self-healing mechanism for unschedulable pods
    • Disable automation
    • Troubleshooting
    • Automation with GitOps
  • Cloud billing integration
    • Connecting AWS CUR
    • Connecting Azure Cost Management
  • Clusters' metrics overview
  • Podfit | vertical pod right-sizing
    • Understanding 'At Risk' indicators
    • LimitRange and ResourceQuota
  • Infrafit | node right-sizing
  • Configure alerts
    • Alerts acknowledgement
  • Trends monitoring
  • Revisions history log
  • Product overview
    • How to monitor PerfectScale Agent
    • PerfectScale data collected
    • PerfectScale Autoscaler Objects' Events
    • Outbound Request Ports used by the Exporter and Autoscaler
    • PerfectScale Weekly Report
    • Product architecture
  • Customizations
    • Alerting
      • Resiliency alerts
      • Financial alerts
    • Pricing
      • Custom Pricing configuration
      • AWS CUR configuration
      • Azure Cost Management configuration
    • Ticketing & Bug Tracking
    • Communication & Messaging
      • Slack Integration
        • How to configure slack_token
        • How to configure routings
      • MS Teams Integration
        • How to configure teams_webhook
      • Datadog Alerts Integration
    • Label customizations
    • Grouping
    • Observability
    • Podfit labels
    • Optimization Policy customization
  • Administration
    • Cluster settings
    • User management
    • Roles and permissions
    • Subscription details
    • Help Center
  • PerfectScale trial
    • How to find your allocated vCPU?
  • PerfectScale Prometheus Exporter
  • Security
    • MFA
    • SSO
    • ps-agent RBAC Permissions
    • psc-autoscaler RBAC Permissions
    • ps-exporter via Proxy Configuration
  • Public API
  • Help PerfectScale to improve
  • Go to your account
Powered by GitBook
LogoLogo

© PerfectScale 2025

On this page
  • What are resiliency alerts
  • How to create Alerts Profile
  • How to apply Alerts Profile
  1. Customizations
  2. Alerting

Resiliency alerts

Resolve resilience risks proactively before they affect your users with impact-driven prioritization

PreviousAlertingNextFinancial alerts

Last updated 1 month ago

What are resiliency alerts

Alerts are designed to quickly identify and notify of relevant indicators changes, ensuring they can be eliminated before impacting the system.

For faster updates, utilize , , or Integrations to receive notifications when an Alert is generated.

By default, PerfectScale generates alerts for every cluster where a with a was identified.

In order to customize your alerts, an must be set up and applied to the cluster. It will override the default alert generation process, ensuring identification and notification about relevant indicator changes.

You can apply only one Resiliency Alert Profile per cluster.

A cluster that transmits data is required to start receiving alerts configured with an Alert Profile.

From the Settings tab.

Go to the Settings tab on the left panel -> select Alerts -> click the +Add Profile button -> name the profile in the corresponding row -> specify the min_risk_level (low, medium, high) and ignored entities (if needed) -> click Save button.

If the min_risk_level is set to medium, only indicators with high or medium severity will trigger alerts.

From the Overview tab

Go to the Overview tab on the left panel -> find the cluster to which you want to apply the Alert Profile and click gear button -> go to Customizations -> click on Add New Profile in the Alerts drop-down list -> name the profile in the corresponding row -> specify the min_risk_level (low, medium, high) and ignored entities (if needed) -> click the Save And Apply button.

Alerts Profile Configuration

  1. Name the profile.

  2. Configure the profile:

    • ignored_entities - allows removing specific workloads, namespaces, and containers from triggering alerts.

Apply to a single cluster

To apply Alert Profile to the cluster, go to the Overview tab on the left panel -> find the cluster to which you want to apply the Alert Profile and click gear button -> go to Customizations -> select the needed profile in the Alerts drop-down list.

Apply to multiple clusters

To apply the profile to multiple clusters from a single view, use the Manage Assignments feature.

Go to the Settings tab on the left panel -> select the Alerts -> click the Manage Assignments button -> apply the profiles for the needed clusters -> click the Save Changes button.

How to create Alerts Profile

There are two options for creating a Profile: or directly .

min_risk_level - the minimum risk level of the issue to trigger the alert. NOTE: if the min_risk_level is set to medium, only indicators with high or medium severity will trigger alerts.

ignored_indicator - allows ignoring certain from triggering alerts.

active_notification_resend - enables the configuration of the active alert resend feature at a specified interval to ensure critical alerts remain visible until addressed. NOTE: active_notification_resend is set to off by default. Examples: active_notification_resend: 5h - resend notifications for active alerts every 5 hours. active_notification_resend: 1d - resend notifications for active alerts every day.

How to apply Alerts Profile

NOTE: You can easily manage your profiles (create, delete), but deleting such profiles is impossible if the profile is already connected to the cluster. Change the profile to default or any other, and only after that remove the current. If you change the Alert Profile to 'None', it will use the default action for alert generation (detected with a ).

If you want to stop generating alerts to your communication channels, disconnect the messaging profile from the cluster (, ).

🛠️
💡
💡
👉
🛠️
Slack
MS Teams
from the Settings tab
from the Overview
💡
resilience indicator
min_risk_level: high
Slack
MS Teams
DataDog Alerts
resilience indicator
Alerts Profile
min_risk_level: high
types of issues
Resiliency alerts profile
Resiliency alerts profile from settings
Resiliency alerts profile from overview
Resiliency alerts profile configuration
Applying resiliency alerts profile to a single cluster