Navigate to Management > System Settings to access the unified System Settings screen. This screen presents all platform configuration parameters, default limits, and system constraints grouped across 8 tabs.
uyarı
Only users with the Administrator (Admin) role can access this screen. Settings should be configured carefully as they are effective platform-wide.
The unified System Settings page merges General Settings, System Properties (previously managed on separate screens) along with previously undocumented runtime parameters and system constraints into a single interface. Each setting has a scope badge:
Scope
Color
Description
Deploy Required
Orange
Stored in database, API Proxies must be redeployed for changes to take effect
Restart Required
Blue
Defined as environment variable, pod restart required for changes
Fixed
Gray
Immutable infrastructure limit
Editable settings can be modified directly from the screen using appropriate input controls (number, text, toggle, color picker, etc.). Read-only parameters are shown with a lock icon.
Log retention settings determine storage duration and maximum record counts for different log types. Separately configurable for all log types (traffic, application, token, audit, login), including Identity Synchronization History — the durable run-by-run log described in Credential Synchronization, disabled by default so no run record is deleted until an administrator turns it on.
Log Retention above decides how long log records are kept; the Data Retention Profile answers a different question — whether a request's body/headers get captured at all. There are three profiles, increasing in strictness:
Profile
Label on screen
Behavior
STANDARD
Standard
Today's behavior — body/header capture, persistence, and tracing all work normally per your existing settings
NO_PAYLOAD
No Payload
Request/response headers, query string, and body are never captured — not scrubbed afterward, simply never populated. Starting Live Trace is locked under this profile; not even an authorized user can turn it on
NO_PERSIST
No Persist
Everything No Payload restricts, plus no record at all is sent to connectors, the Mongo trace store, or OTel spans. Tracing is locked here too
Counter and metric flows (Prometheus, quota counters) are unaffected by all three profiles — these profiles only stop persistent record creation, not counting.
Not the Same as In-Memory Data
These profiles prevent persistent/external record creation. While a request is being processed, the data still exists temporarily in JVM memory (for example, while being forwarded to the backend) — these profiles do not establish a claim that "no trace exists even in memory," only that "no persistent/external record is created."
The profile can be set at three levels: the global level on this page, the project settings level, and the API proxy's traffic log settings level. The effective profile is the strictest of the three levels — a lower level can never choose a looser profile than the level above it: a project can match the global profile or be stricter than it; a proxy must likewise match or exceed the effective profile it inherits (global + project). Choosing a looser profile is rejected on save.
This cascade isn't just a UI convenience — the gateway computes the effective profile at runtime with the same strictest-wins logic, so trying to bypass a higher level outside the UI (for example, updating a proxy's setting directly through APIops) has no effect.
Installation-wide defaults for the circuit breaker that protects log delivery over Kafka, RabbitMQ, ActiveMQ, Graylog, Webhook, and database (DB) connections. This section is independent of the Routing circuit breaker on Tab 1 — that one governs requests routed to backends; this one only covers connector log delivery.
Parameter
Default
Configuration Range
Scope
Circuit Breaker Enabled
Disabled
-
Deploy Required
Error Window
10 s
1 - 3,600 s
Deploy Required
Error Threshold
5
1 - 10,000
Deploy Required
Sleep Window
30 s
1 - 3,600 s
Deploy Required
Half-Open Attempt Enabled
Enabled
-
Deploy Required
bilgi
These five values are installation-wide defaults. Circuit Breaker Enabled, Error Threshold, and Sleep Window can be overridden per connection from the Resilience (Circuit Breaker) section on the Kafka, RabbitMQ, ActiveMQ, Graylog, Webhook, and database connection screens; fields left empty inherit the defaults configured here. Error Window and Half-Open Attempt Enabled are configured only here, installation-wide.