Skip to content

Content: Missing Guide for Autoscaling Feature #852

Open

Description

@wowi42

Prerequisites check

  • I have searched existing documentation to verify this content doesn't already exist
  • I have checked for existing issues for this request

Type of content requested

Documentation

Content description

Problem Statement

The autoscaling feature on Clever Cloud lacks official documentation, creating confusion for users who want to:

  • Understand how autoscaling works (triggers, limits, behavior).
  • Configure it properly for their applications.
  • Troubleshoot common issues (e.g., unexpected scaling, cost implications).

Customer Impact:

  • Users rely on trial-and-error or community forums, leading to suboptimal configurations.
  • Risk of misconfigured apps (over/under-scaling) due to unclear guidelines.

Proposed Solution

Create a dedicated documentation page covering:

  1. Concepts:
    • How autoscaling is triggered (CPU, RAM, requests, etc.).
    • Default thresholds and customization options.
    • Interaction with other features (e.g., vertical scaling, add-ons).

Expected Benefits

For Users For Clever Cloud
✅ Clear guidance for setup ❌ Fewer support requests
✅ Reduced misconfigurations 📊 Better user adoption of the feature
✅ Faster troubleshooting 🔄 Lower operational overhead

Origin: Identified as a gap during customer onboarding and support interactions.
Labels: documentation, autoscaling, ux-improvement, customer-request

Use case and target audience

No response

Technical details (for framework guides)

No response

Additional context (optional)

No response

Activity

  1. added
    enhancementNew content, a new feature, or an improvement to existing documentation
    on Dec 9, 2025
  2. added
    needs infoMore information is required before the issue can be acted on
    on Aug 26, 2026
  3. self-assigned this
    on Aug 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew content, a new feature, or an improvement to existing documentationneeds infoMore information is required before the issue can be acted on

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions