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
  1. Product overview

PerfectScale data collected

Explore what the data PerfectScale collects in order to provide service

In order to provide service, PerfectScale collects the following data:

  1. cAdvisor metrics:

    container_cpu_cfs_periods_total
    container_cpu_cfs_throttled_periods_total
    container_cpu_usage_seconds_total
    container_memory_working_set_bytes
    container_network_receive_bytes_total
    container_network_transmit_bytes_total
    
  2. kube-state-metrics metrics:

    kube_pod_labels
    kube_pod_annotations
    kube_pod_info
    kube_pod_container_status_running
    kube_pod_container_status_terminated
    kube_pod_container_status_terminated_reason
    kube_pod_container_status_last_terminated_reason
    kube_pod_container_resource_requests
    kube_pod_container_resource_limits
    kube_pod_container_status_restarts_total
    kube_pod_start_time
    kube_pod_completion_time
    kube_node_info
    kube_node_status_capacity
    kube_node_status_allocatable
    kube_node_status_condition
    kube_node_labels
    kube_pod_status_phase
    kube_job_owner
    kube_replicaset_owner
    kube_horizontalpodautoscaler_info
    kube_horizontalpodautoscaler_labels
    kube_horizontalpodautoscaler_spec_target_metric
    kube_horizontalpodautoscaler_spec_min_replicas
    kube_horizontalpodautoscaler_spec_max_replicas
    kube_horizontalpodautoscaler_status_desired_replicas
    kube_horizontalpodautoscaler_status_current_replicas
    kube_pod_container_info
    kube_namespace_labels
    kube_pod_status_reason
    kube_job_status_failed
  3. The data about containers’ spec (original) resources (spec CPU&Memory Requests&Limits) from kubeapiserver.

PreviousHow to monitor PerfectScale AgentNextPerfectScale Autoscaler Objects' Events

Last updated 1 year ago