Kfuse Profiler Server (Continuous Profiling)

Enable kfuse-profiling in custom-values.yaml file -

global:
  kfuse-profiling:
    enabled: true

By default, the data will be saved in the PVC with size of 50GB.

Long-Term Retention

To retain profiling data for a longer duration, additional configuration is required. Depending on the storage provider, configure one of the following options in the custom-values.yaml file:

For AWS S3 Storage:
Add the necessary AWS S3 configuration to store profiles.
For GCP Bucket:
Include the required GCP Bucket configuration to store profiles data.

Note: Profiles are stored in parquet format on AWS or GCP.

pyroscope:
  pyroscope:
    # Add support for storage in s3 and gcs for saving profiles data
        
    # Additional configuration is needed depending on where the storage is hosted (AWS S3 or GCP GCS)
    # Choose the appropriate configuration based on your storage provider.
    
    # AWS S3 Configuration Instructions:
    # 1. Set the 'backend' to 's3'
    # 2. Configure the following S3-specific settings:
    #    - bucket_name: Name of your S3 bucket
    #    - region: AWS region where your bucket is located
    #    - endpoint: S3 endpoint for your region
    #    - access_key_id: Your AWS access key ID
    #    - secret_access_key: Your AWS secret access key
    #    - insecure: Set to true if using HTTP instead of HTTPS (not recommended for production)
    
    # Example AWS S3 configuration:
    config: |
      storage:
        backend: s3
        s3:
          bucket_name: your-bucket-name
          region: us-west-2
          endpoint: s3.us-west-2.amazonaws.com
          access_key_id: YOUR_ACCESS_KEY_ID
          secret_access_key: YOUR_SECRET_ACCESS_KEY
          insecure: false
    
    # GCP GCS Configuration Instructions:
    # 1. Set the 'backend' to 'gcs'
    # 2. Configure the following GCS-specific settings:
    #    - bucket_name: Name of your GCS bucket
    #    - service_account: JSON key file for your GCP service account
    
    # Prerequisites for GCP GCS:
    # - Create a GCP service account with access to the GCS bucket
    # - Download the JSON key file for the service account
    
    # Example GCP GCS configuration:
    config: |
      storage:
        backend: gcs
        gcs:
          bucket_name: your-gcs-bucket-name
          service_account: |
            {
              "type": "service_account",
              "project_id": "your-project-id",
              "private_key_id": "your-private-key-id",
              "private_key": "-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----\n",
              "client_email": "your-service-account-email@your-project-id.iam.gserviceaccount.com",
              "client_id": "your-client-id",
              "auth_uri": "https://accounts.google.com/o/oauth2/auth",
              "token_uri": "https://oauth2.googleapis.com/token",
              "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
              "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/your-service-account-email%40your-project-id.iam.gserviceaccount.com",
              "universe_domain": "googleapis.com"
            }