What the data for this category looks like
Data sources for this category include switch consoles, wireless controllers, office monitoring systems, and end-user trouble reports. Updates occur daily or after each network change. Daily maintenance documents include network topology diagrams, change orders, fault records, and wireless coverage inspection forms. Data fields include fault occurrence time, connected AP number, associated VLAN, terminal MAC address, and contact information for the person submitting the fault report. No additional statistical quantitative metrics are included.
What constraints these characteristics impose during deployment and upgrade
This category’s data sources are scattered and depend on hardware devices and manual trouble reports. During deployment, reserve configuration items for connecting multiple data sources to ensure access to the log interfaces of switches and wireless controllers. Daily maintenance document structures are fixed. Deployment must support importing standardized network topology and inspection form files. Data update frequency changes dynamically based on maintenance actions. During upgrade, ensure the data synchronization service does not interrupt to avoid data loss during fault troubleshooting. Fault record fields must align with maintenance workflows. Deployment configuration must support custom field mapping rules to adapt to the maintenance document formats of different enterprises.
How to set the configuration
The following configurations are compatible with FastGPT v4.17.0.
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://admin:password@internal-db:27017/fastgpt?authSource=admin | Stores structured and unstructured operational data including fault records and topology diagrams. The default port 27017 must not have port conflicts with other internal network services |
PG_URL | postgresql://admin:password@internal-db:5432/fastgpt | Stores structured metadata for maintenance change orders and inspection forms. The default port 5432 aligns with enterprise internal database deployment practices |
REDIS_URL | redis://:cachepass@internal-cache:6379/0 | Caches real-time fault alerts and user trouble report information. Database index 0 avoids conflicts with other business caches |
DB_MAX_LINK | 20–30 connections | Adapts to the volume of inspection forms and fault log data imported in daily batches, preventing database connection exhaustion from impacting maintenance response |
FE_DOMAIN | https://fastgpt.internal-net.com | Provides internal access entry for the fault troubleshooting tool. Must match enterprise internal DNS configuration |
FILE_TOKEN_KEY | Randomly generated 64-bit string | Encrypts stored uploaded files including network topology diagrams and inspection forms, preventing unauthorized access to maintenance documents |
ROOT_KEY | Randomly generated 32-bit string | Configures system administrator access keys for initializing the maintenance management interface |
Three common issues
- Issue: After Docker deployment and a power loss restart, PostgreSQL or MongoDB services fail to start. Logs display connection refused or database file corruption errors. Cause: Container data volume persistent storage was not configured, and power loss resulted in loss of in-memory database files.
- Issue: After configuring
MONGODB_URI, wireless controller logs cannot be imported, and the interface shows connection timeout. Cause: The MongoDB port was not opened to the internal network, and the network segment where the wireless controller is located cannot access the database service. - Issue: After local Docker Compose deployment, new users cannot be created, and the administrator interface has no user management entry. Cause:
ROOT_KEYwas not configured correctly, or the system administrator initialization process was not executed, preventing access to background management permissions.
How to confirm the configuration is complete
- Run the built-in database connectivity test tool to verify connectivity for the
MONGODB_URIandPG_URLconfigurations, confirming that stored maintenance data can be read. - Upload a standard-format wireless coverage inspection form to verify that file upload and parsing functions work normally, confirming that the
FILE_TOKEN_KEYconfiguration is valid. - Simulate an end-user submitting a trouble report, check whether the system generates a corresponding fault record and pushes it to the maintenance interface, confirming that the
REDIS_URLcache function works normally. - Access the internal domain name corresponding to
FE_DOMAIN, confirm that the maintenance tool interface loads normally, verifying that the domain name configuration is correct.
The values provided are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.