Feb 11, 2025

Feb 11, 2025

CLI Version 0.24.3 & Autoscaling Updates

CLI Version 0.24.3 & Autoscaling Updates

CLI Updates:

  • In an effort to improve the CLI and better understand how customers are using it we have added telemetry to our commands. This telemetry data is being sent to an internal system that we are already using throughout our platform, but users might see an extra request being sent to tuna.aptible.com when a command is being run.

  • We have significantly improved performance of our commands that list resources (e.g. environment:list, apps, db:list, endpoints:list, log_drain:list , and metric_drain:list )


Install the latest version of the CLI here.


Other releases improvements:

  • Autoscaling Update: The Post Release Cooldown scaling policy configuration will now always ignore this period of time following a release in the metrics used to evaluate scaling, even if it would be included in the current lookback. You can now use this setting to ignore spiky CPU/memory usage on service startup without having to tune your lookback. The default has also been lowered from 5 minutes to 1 minute. Note: This setting is available on both Horizontal and Vertical Autoscaling.

CLI Updates:

  • In an effort to improve the CLI and better understand how customers are using it we have added telemetry to our commands. This telemetry data is being sent to an internal system that we are already using throughout our platform, but users might see an extra request being sent to tuna.aptible.com when a command is being run.

  • We have significantly improved performance of our commands that list resources (e.g. environment:list, apps, db:list, endpoints:list, log_drain:list , and metric_drain:list )


Install the latest version of the CLI here.


Other releases improvements:

  • Autoscaling Update: The Post Release Cooldown scaling policy configuration will now always ignore this period of time following a release in the metrics used to evaluate scaling, even if it would be included in the current lookback. You can now use this setting to ignore spiky CPU/memory usage on service startup without having to tune your lookback. The default has also been lowered from 5 minutes to 1 minute. Note: This setting is available on both Horizontal and Vertical Autoscaling.

CLI Updates:

  • In an effort to improve the CLI and better understand how customers are using it we have added telemetry to our commands. This telemetry data is being sent to an internal system that we are already using throughout our platform, but users might see an extra request being sent to tuna.aptible.com when a command is being run.

  • We have significantly improved performance of our commands that list resources (e.g. environment:list, apps, db:list, endpoints:list, log_drain:list , and metric_drain:list )


Install the latest version of the CLI here.


Other releases improvements:

  • Autoscaling Update: The Post Release Cooldown scaling policy configuration will now always ignore this period of time following a release in the metrics used to evaluate scaling, even if it would be included in the current lookback. You can now use this setting to ignore spiky CPU/memory usage on service startup without having to tune your lookback. The default has also been lowered from 5 minutes to 1 minute. Note: This setting is available on both Horizontal and Vertical Autoscaling.

CLI Updates:

  • In an effort to improve the CLI and better understand how customers are using it we have added telemetry to our commands. This telemetry data is being sent to an internal system that we are already using throughout our platform, but users might see an extra request being sent to tuna.aptible.com when a command is being run.

  • We have significantly improved performance of our commands that list resources (e.g. environment:list, apps, db:list, endpoints:list, log_drain:list , and metric_drain:list )


Install the latest version of the CLI here.


Other releases improvements:

  • Autoscaling Update: The Post Release Cooldown scaling policy configuration will now always ignore this period of time following a release in the metrics used to evaluate scaling, even if it would be included in the current lookback. You can now use this setting to ignore spiky CPU/memory usage on service startup without having to tune your lookback. The default has also been lowered from 5 minutes to 1 minute. Note: This setting is available on both Horizontal and Vertical Autoscaling.

548 Market St #75826 San Francisco, CA 94104

© 2025. All rights reserved. Privacy Policy

548 Market St #75826 San Francisco, CA 94104

© 2025. All rights reserved. Privacy Policy

548 Market St #75826 San Francisco, CA 94104

© 2025. All rights reserved. Privacy Policy

548 Market St #75826 San Francisco, CA 94104

© 2025. All rights reserved. Privacy Policy