Configuration

Path: Left sidebar > Advanced > Configuration

The Configuration page exposes the complete Ceph configuration database across all daemon types. Changes made here are written to the monitor config database and then distributed to running daemons without restart in most cases.

Dashboard Overview

Use this page to inspect tunable parameters, validate current overrides, and apply controlled config-database changes for Ceph daemons.

Note

The total option count shown in the header is environment-specific (for example Configuration Options (1907) in the reference UI).

What This Screenshot Shows: Configuration Dashboard (UI Reference; Values Depend On Your Environment).

Actions in This Screen

Header Control	What It Does
Search bar (Search configuration options...)	Filters the option list in real time by keyword or parameter name
All Filters dropdown	Opens filters for Section and Level
Configuration Options count	Shows total parameters currently available in the config database

Configuration List - Column Reference

Column	What It Shows
Name	Configuration key (for example admin_socket, osd_memory_target)
Description	Short explanation of the parameter (expand row for full text)
Section	Target daemon group (for example global, mon, mgr, osd, mds, client, rgw)
Current Value	Current override in the database. - means no override.
Default Value	Compiled default used when no override exists
Editable	Yes means the value can be changed from this UI

Filters

Filter	Description
Section	Filter by daemon type (for example global, osd, mon, mgr, mds, client, rgw)
Level	Show basic, advanced, or all settings
Search	Find settings by key name or keyword

How To Find A Configuration Parameter

Purpose:

• To locate exact settings for tuning, validation, or troubleshooting.

When to Use:

• Before editing any parameter.

• During root-cause analysis of daemon behavior.

Steps:

1. Open Advanced > Configuration.

2. Use Search configuration options... with a parameter name or keyword.

3. Optionally open All Filters.

4. Filter by Section and Level to narrow scope.

Expected Outcome:

• You get a focused list of relevant parameters.

How To View Full Parameter Details

1. Find the parameter in the list.

2. Click chevron > to expand the row.

3. Review all parameter metadata in the expanded detail panel.

Expanded Row - Field Reference:

Field	What It Shows
Name	Full parameter key name
Description	Full short description
Long Description	Extended detail (can be - if not provided)
Type	Data type (for example str, int, float, bool)
Default	Compiled default value
Min / Max	Allowed numeric bounds (blank when not defined)
Daemon	Daemon-visible value rendering
Level	Parameter complexity level (basic, advanced, dev)
Tags	Feature tags (or -)
Flags	Internal behavior flags (for example ["startup"])
Services	Daemon group scope (for example common)

TOOLTIP - Flags = ["startup"]:

• Startup-flagged parameters only take effect on daemon restart.

• Current Value can update immediately while daemon behavior remains old.

• Restart the affected daemon to apply runtime behavior.

How To Edit A Configuration Value

Purpose:

• To tune daemon behavior or apply a targeted operational change.

When to Use:

• During controlled maintenance or validated tuning windows.

Steps:

1. Find the target parameter.

2. Confirm Editable = Yes.

3. Click the row edit action (or expand row with chevron > and click Edit Value).

4. Enter new value and confirm.

What Happens After Editing:

• New value is written to monitor config database immediately.

• Current Value updates to show active override.

• Most parameters propagate without restart.

• ["startup"] parameters still require daemon restart.

Warning

Only edit parameters you understand. advanced and dev level changes can destabilize cluster behavior.

How To Reset A Value To Default

1. Expand the parameter row.

2. Click Edit Value.

3. Clear the value field completely.

4. Confirm.

Expected Outcome:

• Override is removed.

• Current Value returns to -.

• Daemon falls back to the compiled Default Value.

Common Tasks

Edit and reset tasks are covered in:

• Edit A Configuration Value

• Reset A Value To Default

Add A Setting:

• If your release shows an Add Setting action in the page header, use it to enter the key, section, and value for a parameter not currently listed.

• If no Add Setting action is visible, that workflow is not enabled in the current UI build; use the existing parameter list only.

Key Parameters Reference

Parameter	Section	What It Controls
osd_memory_target	osd	Target OSD memory usage and cache behavior
osd_recovery_op_priority	osd	Recovery I/O priority relative to client I/O
mon_osd_down_out_interval	mon	Time before down OSD is auto-marked out
rgw_thread_pool_size	rgw	RGW worker thread count for object traffic
mds_cache_memory_limit	mds	Maximum metadata cache size per MDS daemon

Cautions

• advanced and dev settings can destabilize the cluster. Change only with documentation-backed guidance.

• Some changes require daemon restart to take effect even when Current Value updates (for example startup-flagged parameters).

• Monitor config database overrides /etc/ceph/ceph.conf entries for the same key. The file acts as fallback for bootstrap settings.

If this fails

Problem You See	Most Likely Cause	What To Do
Cannot find parameter	Wrong keyword or unknown exact name	Use shorter keywords and apply Section filter
Editable shows No	Read-only from dashboard	Apply through administrator CLI workflow
Value changed but behavior did not	Startup-flagged parameter	Check Flags; restart affected daemon if needed
Cluster became unstable after change	Unsafe parameter value	Revert immediately by clearing override to default

Note

If issues persist, raise a support ticket via Monitoring > Alerts or the Karios Support.