update

dpsctl settings update Usage Guide

Update global DPS settings.

Usage

dpsctl settings update

Flags

Includes global dpsctl options.

   --set value          Setting to update (format: key=value). Can be specified multiple times.
   --help, -h           show help

Examples

Update Single Setting

$ dpsctl settings update --set prs_enabled=false
{
  "status": {
    "diag_msg": "Success",
    "ok": true
  },
  "updated_settings": {
    "prs_enabled": "false"
  }
}

Update Multiple Settings

$ dpsctl settings update --set prs_enabled=false --set metrics_interval_seconds=30
{
  "status": {
    "diag_msg": "Success",
    "ok": true
  },
  "updated_settings": {
    "metrics_interval_seconds": "30",
    "prs_enabled": "false"
  }
}

Update PRS Headroom

Set the deployment-wide PRS headroom percentage, then read it back:

$ dpsctl settings update --set prs_headroom_percent=-15
{
  "status": {
    "diag_msg": "Success",
    "ok": true
  },
  "updated_settings": {
    "prs_headroom_percent": "-15"
  }
}

$ dpsctl settings list | jq -r '.settings.prs_headroom_percent'
-15

prs_headroom_percent must be a finite number from -50 through 100, inclusive. Negative headroom is generally recommended for responsive PRS steering, and -30 is the tested starting point for DPS 0.8.x. See Power Reservation Steering for the full tuning guidance and the meaning of negative, zero, and positive values.

Notes

• Changes are persisted immediately unless otherwise noted
• Invalid setting names or values will result in an error
• Some settings may require specific formats (e.g., duration values like “30s”, “5m”)
• Use dpsctl settings list to see current values before updating
• A persisted prs_headroom_percent overrides the Helm dps.prs.headroomPercent default on subsequent server restarts until it is updated again
• When prs_enabled is true, changing the effective prs_headroom_percent triggers an asynchronous re-upsert of active PRS domains and does not require a server restart. A successful command confirms that the setting was stored; check the DPS server logs to confirm that the background PRS re-upsert completed. Writing the existing value is a no-op and produces no new re-upsert log