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
  • routings_by_id
  • routings
  • Slack Routing Configuration
  1. Customizations
  2. Communication & Messaging
  3. Slack Integration

How to configure routings

Learn how to configure Slack routings

PreviousHow to configure slack_tokenNextMS Teams Integration

Last updated 1 month ago

Routings for Slack notifications enable sending alerts to different Slack channels for various workloads within a cluster based on labels.

slack_token: ''
channel_id: ''
routings_by_id:
  - label_key_1
  - label_key_2
routings:
  - label_key_3
  - label_key_4     

To maximize your effectiveness, Slack routing is available not on the workload level only, but also on the namespace level. This means you can configure routing for specific workloads as well as for the entire namespace.

Workload labels take precedence over namespace labels. If you set a routing label for a workload that differs from the label for its namespace, PerfectScale will send Alerts to the channel specified for the workload.

There are two options on how to configure Slack routing:

  • By specifying the where you want to receive Slack Alerts.

  • By specifying the where you want to receive Slack Alerts.

PerfectScale strongly recommends configuring routing by specifying the to ensure seamless work of the configuration.

routings_by_id

To configure routings with the channel ID, define the labels matching the Slack channel ID you want to receive Slack Alerts.

Example of a label:

label_some_key : label_some_value, where label_some_value = Slack channel ID

routings

To configure routings with the channel name, define the labels matching the Slack channel names you want to receive Slack Alerts.

label_some_key : label_some_value, where label_some_value = Slack channel name

If the value of a label with a key label_key is wrong or empty, PerfectScale will send Alerts to the Slack channel specified in the channel_id row.

Slack Routing Configuration

  1. Name the profile.

  2. Indicate the channel_id. This field is mandatory, and the indicated channel will be the default channel if Advanced Alert Routing fails.

  3. List label_key(s) under routings_by_id (to configure routing by channel_id) or routings (to configure routing by channel_name).

  4. Verify if your Slack is configured properly with the Test Integration button.

  5. Click Save button.

Example of a label:

Ensure to configure slack_token and include the relevant data in the field. This field is mandatory.

💡
slack_token
💡
Slack channel IDs
Slack channel names
Slack channel IDs