What data for this category looks like
Business process data for power grid enterprises comes from internal business systems such as marketing and business halls. Updates have no fixed schedule. They are triggered when new business processes go live or policies are adjusted. Data is categorized by business type. Each entry includes business code, process step serial number, step name, required materials, and processing time limit. Step serial numbers are unitless integers. Processing time limits are measured in workdays. Material lists are structured text entries.
Constraints during deployment and upgrade
Grid enterprise business handling data is structured business process data. It must be obtained via integration with internal systems. Updates have no fixed schedule. During deployment, support for dynamic data source configuration is required to avoid hardcoding process rules. Field mapping rules must be configured to convert fields from internal systems such as business codes and step serial numbers into a format recognizable by FastGPT. During upgrade, compatibility with older data formats is required to prevent process guidance errors caused by field changes. Data storage compliance requirements must also be met. Prioritize local or compliant internal network cloud storage paths.
Configuration settings
Reference only; verify against the target FastGPT release and deployment documentation.
| Configuration Item | Recommended Approach | Basis for This Approach |
|---|---|---|
MONGODB_URI | mongodb://<username>:<password>@<internal-host1>:<port1>,<internal-host2>:<port2>/grid_business?replicaSet=rs0 | Grid business data requires persistent storage. Compliant clusters ensure data security and high availability |
REDIS_URL | redis://:<password>@<internal-redis-service>:6379/0 | Cache business process data and session information. Internal network deployment meets compliance requirements |
DB_MAX_LINK | 200–300 connections | Grid business handling traffic fluctuates significantly. A reasonable number of connections ensures concurrent processing capability and prevents resource exhaustion |
FE_DOMAIN | https://internal-service.grid.com | Restrict front-end access domain names to ensure access security for internal services |
STORAGE_S3_ENDPOINT | http://internal-s3.grid.com:9000 | Store business process documents and user consultation records to meet data storage compliance requirements |
FILE_TOKEN_KEY | Randomly generated string of 32 or more characters | Serve as an authentication key for file access to ensure access security for internal file resources |
Three common mistakes
- Symptom: Database connection failure after container startup. Logs show
connection refusedorauthentication failed. Cause: Incorrect authentication information forMONGODB_URIis not configured, or the database service does not allow internal network access permissions. - Symptom: Front-end pages cannot access the specified port. No obvious errors appear in container logs. Cause:
FE_DOMAINis not correctly configured as an internal network accessible domain name, or a firewall blocks internal network traffic on the corresponding port. - Symptom: Imported business process data fails to load completely. Some steps are missing. Cause: Correct field mapping rules are not configured, causing some business fields from internal systems to not be recognized by FastGPT.
How to confirm correct configuration
- Run the
docker pscommand to confirm that all FastGPT-related containers are in a running state. - Access the configured
FE_DOMAINto confirm that the front-end page loads normally and displays the login entry. - Enter the system backend, test importing a piece of grid enterprise business process data, and confirm that the data is correctly parsed and the complete process steps are displayed.
- Check database connection monitoring metrics to confirm that the current number of connections does not exceed the threshold set by the
DB_MAX_LINKconfiguration.
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-09-28.