Configuration options for strategies
You can customize how a deployment strategy behaves in Platform Settings > Deployment Strategies. Each strategy includes configurable settings that control rollback triggers, telemetry-based monitoring, and traffic pacing.
These options let you:
- Define automatic rollback rules based on metrics
- Choose which telemetry signals to monitor during rollout
- Adjust how quickly traffic shifts from one version to another
Configure rollback with metrics
Set up automatic rollback triggered by telemetry signals:
- Metric name – e.g.,
http.error_rate - Threshold – Numeric value that triggers rollback
- Comparison –
greater_than,less_than, orequal
How often nullplatform checks metrics
- First 5 minutes: Every 30 seconds (fast detection during initial rollout)
- After 5 minutes: Every 1 minute
- After 2 hours or once the deployment is finalized: Checks stop automatically
This approach balances quick detection with system performance.
Reference: available metrics by deployment type
Kubernetes, Container, and instance-based deployments
| Metric name | Description |
|---|---|
system.memory_usage_percentage | Percentage of memory usage on the instance |
http.response_time | Average HTTP response time in milliseconds |
system.cpu_usage_percentage | Percentage of CPU usage on the instance |
http.healthcheck_fail | Number of failed health checks within the evaluation window |
http.rpm | Number of HTTP requests per minute |
http.error_rate | Rate of HTTP 4xx & 5xx errors over total requests |
http.healthcheck_count | Total number of health checks performed |
Serverless deployments
| Metric name | Description |
|---|---|
serverless.throttles | Number of throttled executions due to concurrency or rate limits |
serverless.concurrent_executions | Number of concurrent executions in progress |
serverless.invocations | Total number of function invocations |
serverless.duration | Average duration of function executions in milliseconds |
serverless.errors | Total number of failed invocations due to errors |
Configure traffic pacing
Configure gradual traffic shifting:
- Interval – Time between increments (e.g., 30s)
- Step size – Percentage of traffic per step (e.g., 10%)