Skip to content
rConfig Documentation

System Settings Reference

System Settings Reference: Configuration and Administration Guide for rConfig V8

Section titled “System Settings Reference: Configuration and Administration Guide for rConfig V8”

The System Settings interface in rConfig V8 provides centralized access to all configuration, security, maintenance, and administrative functions. This reference guide maps each settings section to its purpose and detailed documentation, enabling administrators to quickly locate configuration areas and understand their impact on system operations.

Organizations can use this reference to navigate system configuration efficiently, understand relationships between settings sections, and maintain consistent administrative practices across deployment lifecycle.

Getting Started

Section titled “Getting Started”

Settings sections for initial system configuration and ongoing assistance.

System Management

Section titled “System Management”

Core system configuration, maintenance, and operational settings.

System

Section titled “System”

Purpose: General system configuration including application name, timezone, date formats, and default user preferences.

Key Settings:

  • Application name and branding
  • Timezone configuration for timestamps
  • Date and time display formats
  • Email settings
  • User interface preferences

When to Use: During initial deployment to configure organizational standards, or when adjusting system-wide display and behavior preferences.

Related Documentation: PLACEHOLDER - System Configuration Guide

Upgrade

Section titled “Upgrade”

Purpose: In-place system upgrade management for updating rConfig to newer versions.

Key Functions:

  • Check for available updates
  • View release notes V8 PRO - Enterprise Edition
  • Execute upgrade process with our sales

When to Use: When new rConfig versions are released with features, improvements, or security updates requiring deployment.

Related Documentation: PLACEHOLDER - Upgrade Procedures Guide

Security & Access

Section titled “Security & Access”

Authentication, authorization, and security hardening configuration.

Security

Section titled “Security”

Purpose: System security settings including password policies, session management, encryption, and security hardening options.

Key Settings:

  • Password complexity requirements
  • Password expiration and rotation policies
  • Session timeout and concurrent session limits
  • Two-factor authentication (2FA) configuration
  • API rate limiting
  • Security headers and HTTPS enforcement
  • Audit logging configuration

When to Use: During initial deployment to establish security baseline, when implementing compliance requirements, or when hardening system against security threats.

Related Documentation:

  • System Encryption Key - Encryption key management and rotation
  • PLACEHOLDER - Security Best Practices Guide

Device Credentials

Section titled “Device Credentials”

Purpose: Management of authentication credentials used for connecting to network devices.

Key Functions:

  • Create and manage credential sets
  • Configure SSH passwords and private keys
  • Set Telnet passwords
  • Configure SNMP community strings and v3 credentials
  • Enable password configuration
  • Credential assignment to devices

When to Use: When adding new devices requiring different credentials, rotating device passwords, or organizing credentials by device groups or security zones.

Related Documentation: PLACEHOLDER - Device Credentials Management Guide

Data Management

Section titled “Data Management”

Migration, and data lifecycle management.

Data Migration

Section titled “Data Migration”

Purpose: Migration tools for upgrading from previous rConfig versions or moving between deployments.

Key Functions:

  • Database migration from older versions
  • Configuration file migration
  • User account migration
  • Policy and compliance data migration
  • Integration configuration migration

When to Use: When upgrading from rConfig V6 or V7 to V8, migrating to new infrastructure, or consolidating multiple rConfig instances.

Related Documentation: PLACEHOLDER - Migration Guide

Monitoring & Debugging

Section titled “Monitoring & Debugging”

Logging, monitoring, and diagnostic configuration.

Logging & Debugging

Section titled “Logging & Debugging”

Purpose: Configuration of logging levels, debug modes, and diagnostic tools for troubleshooting.

Key Settings:

  • Log level configuration (emergency, alert, critical, error, warning, notice, info, debug)
  • Debug mode enabling for verbose output
  • Log file rotation settings
  • Performance profiling tools
  • Query logging for database optimization

When to Use: When troubleshooting system issues, investigating performance problems, or gathering detailed diagnostic information for support requests.

Related Documentation:

Application Logs

Section titled “Application Logs”

Purpose: Access to database-driven application event logs for operational monitoring and troubleshooting.

Key Functions:

  • View and filter application events
  • Search log descriptions by keyword
  • Filter by severity level
  • Export logs for external analysis
  • Configure log archival policies

When to Use: When investigating device connection issues, reviewing user activity, monitoring scheduled task execution, or troubleshooting application-level errors.

Related Documentation:

Scheduled Tasks

Section titled “Scheduled Tasks”

Purpose: Management and monitoring of scheduled background tasks including configuration downloads, compliance checks, and maintenance operations.

Key Functions:

  • View task execution history
  • Monitor task success/failure rates
  • Configure task schedules
  • Enable/disable tasks
  • Task performance metrics

When to Use: When reviewing task execution status, troubleshooting scheduled task failures, or optimizing task scheduling for performance.

Related Documentation:

Health Checks (Environment)

Section titled “Health Checks (Environment)”

Purpose: Configure connectivity health checks for online, internal-only, and air-gapped deployments to avoid false-positive failures.

What Changed:

  • External ping checks are now configurable through environment variables
  • Connectivity ping checks can be disabled entirely
  • Deployments can be explicitly marked as offline or air-gapped
  • Internal-only ping targets (such as localhost or a gateway) are supported

Available Settings:

SettingDefaultPurpose
HEALTHCHECK_PING_ENABLEDtrueMaster switch for the connectivity ping check. Set to false to disable ping checks completely.
HEALTHCHECK_OFFLINE_MODEfalseMarks the deployment as offline. When true, ping checks are skipped automatically.
HEALTHCHECK_AIR_GAPPEDfalseMarks the deployment as air-gapped. When true, ping checks are skipped automatically.
HEALTHCHECK_PING_TARGEThttps://www.rconfig.comTarget URL/host used by the ping health check. Set to an internal endpoint for isolated networks.
HEALTHCHECK_PING_TIMEOUT5Timeout in seconds for the ping check before it is treated as failed.

Behavior Summary:

  • Ping check runs only when HEALTHCHECK_PING_ENABLED=true and both offline flags are false
  • If either HEALTHCHECK_OFFLINE_MODE=true or HEALTHCHECK_AIR_GAPPED=true, ping check is skipped
  • If ping check is enabled and target is internal, health check validates internal reachability only

Example Configurations:

Disable connectivity ping check entirely:

HEALTHCHECK_PING_ENABLED=false

Air-gapped deployment (automatic ping check skip):

HEALTHCHECK_PING_ENABLED=true
HEALTHCHECK_AIR_GAPPED=true

Internal-only validation (no external dependency):

HEALTHCHECK_PING_ENABLED=true
HEALTHCHECK_PING_TARGET=http://127.0.0.1
HEALTHCHECK_PING_TIMEOUT=3

When to Use: Configure these settings for environments without internet access, segmented internal networks, strict firewall policies, or when health checks should validate internal reachability instead of external internet access.

Info

Section titled “Info”

System information and version details.

About

Section titled “About”

Purpose: System information display including version, license status, system health, and credits.

Information Displayed:

  • rConfig version and build information
  • License status and expiration
  • System health metrics (uptime, resource usage)
  • Installed modules and features
  • Credits and open source licenses
  • Support contact information

When to Use: When verifying system version for support requests, checking license status, reviewing system health at a glance, or accessing support contact information.

Related Documentation: PLACEHOLDER - About rConfig

Settings Navigation Tips

Section titled “Settings Navigation Tips”

Accessing System Settings

Section titled “Accessing System Settings”
  1. Log in to rConfig with an account having Admin role
  2. Navigate to Settings from the main navigation menu (typically gear icon)
  3. Settings sections are organized by category in the left sidebar
  4. Click any section to view and modify its configuration

Search Functionality

Section titled “Search Functionality”

Many System Settings sections include search functionality:

  • Use search fields to quickly locate specific settings
  • Search operates on setting names, descriptions, and values
  • Filters narrow results by category or status

Configuration Best Practices

Section titled “Configuration Best Practices”

Document changes: Before modifying settings, document current values and business justification for changes. This aids troubleshooting and audit compliance.

Test in non-production: When possible, test setting changes in development or staging environments before applying to production systems.

One change at a time: Modify one setting at a time to clearly identify impact of each change. Multiple simultaneous changes complicate troubleshooting.

Review after updates: After rConfig version updates, review System Settings to identify new options or deprecated settings requiring attention.

Backup before major changes: Create system backup before making significant configuration changes enabling rapid rollback if issues arise.

Common Settings Workflows

Section titled “Common Settings Workflows”

Initial deployment configuration:

  1. System → Configure application name, timezone, defaults
  2. Security → Establish password policies, session timeouts
  3. Logging & Debugging → Set appropriate log levels

Regular maintenance review (quarterly):

  1. Security → Review and rotate credentials
  2. Backup Settings → Verify backups executing successfully
  3. About → Check for available updates

Troubleshooting workflow:

  1. Application Logs → Review recent errors and warnings
  2. Logging & Debugging → Temporarily increase log verbosity
  3. Scheduled Tasks → Check task execution history
Section titled “Related Documentation”

Summary

Section titled “Summary”

The System Settings interface provides centralized access to all rConfig V8 configuration, security, maintenance, and administrative functions. This reference guide maps settings sections to their purposes and detailed documentation, enabling efficient navigation and consistent administrative practices.

Key takeaways for effective settings management:

  • Settings are organized by functional area - System Management, Security & Access, Data Management, Monitoring & Debugging, Developer Tools
  • Many sections have dedicated documentation - Follow links to comprehensive guides for detailed implementation procedures
  • Changes require Admin role - Most System Settings sections are restricted to users with administrator privileges
  • Document configuration changes - Maintain records of what changed, why, and when for troubleshooting and compliance
  • Test before production - Validate setting changes in non-production environments when possible

Regular review of System Settings ensures configuration remains aligned with organizational standards, security requirements, and operational needs as deployments evolve and scale. Use this reference as a navigation tool for locating specific configuration areas and accessing detailed implementation documentation.