Skip to main content
Version: 8.3

system.config

New in 8.3.8

API Endpoint Considerations

caution

The table below lists various Gateway resource configuration OpenAPI endpoints that should be called responsibly, as failing to do so may result in issues with your Gateway.

See the API Documentation page for information on viewing API docs.

URL EndpointReason
/openapi#tag/loggingFrequently dumping all logs can cause system instability due to increased memory usage.
/openapi#tag/thread-diagnosticsWhen called, the JVM will be paused to perform the thread dump.
/openapi#tag/config-management/paths/~1data~1api~1v1~1scan-lock~1config/postUpdates to Gateway resources will be prevented until either a timeout occurs, or a Gateway configuration scan is performed.
/openapi#tag/config-management/paths/~1data~1api~1v1~1scan-lock~1projects/postUpdates to projects will be prevented until either a timeout occurs, or a project scan is performed.
/openapi#tag/config-management/paths/~1data~1api~1v1~1scan~1config/postPrompts the system to scan the file system for configuration changes, and releases the config scan lock if applicable. This should typically never be used in a production environment.
/openapi#tag/config-management/paths/~1data~1api~1v1~1scan~1projects/postPrompts the system to scan the file system for project changes, and releases the project scan lock if applicable. This should typically never be used in a production environment, and can cause problems saving projects from the Designer.
/openapi#tag/restart-tasks/paths/~1data~1api~1v1~1restart-tasks~1restart/postRestarts the Gateway, which can be highly destructive if called improperly.
/openapi#tag/thread-diagnostics/paths/~1data~1api~1v1~1diagnostics~1bundle~1generate/postCreates a thread dump and consolidates logs, which can cause system instability due to increased memory usage.

Config Functions

The following functions allow you to configure various aspects of your Gateway configuration.

Functions by Scope