What this category of data looks like
This category of data includes four types of documents: ad creative files, landing page screenshots, audit opinion sheets, and modification records. Data sources include ad delivery platforms, landing page hosting services, product qualification filing systems, and ad compliance clause libraries. Data updates occur daily or in real time. Each creative corresponds to a unique audit process node. Fields include creative ID, delivery channel, compliance check items, audit status, modification traces, and more. There is no unified fixed unit, as values vary by document type. Records generated during the audit must be strongly bound to the corresponding creative to ensure compliance check traceability.
What constraints these characteristics impose on the database and operations link
The four document types have significantly different structures. Storage must support both unstructured creative files and semi-structured audit records. Real-time update requirements require database connection pools to support high-concurrency access. Ad creatives and audit records have a strong association, so cross-table query efficiency and accuracy must be maintained. The compliance clause library requires regular synchronized updates. An incremental update mechanism must be configured to reduce resource consumption from full synchronization. Modification records generated during the audit must be immutable. Database transactions must be enabled to ensure data consistency. Risk events such as ad rejection require rapid association with corresponding creative data. Index structures must be optimized to improve query speed. Data volume grows continuously alongside delivery volume. Storage and connection expansion space must be reserved to avoid audit task interruptions caused by insufficient resources.
How to set the configurations
This content is based on FastGPT v4.17.0. Below are database and operations configuration recommendations for the ad creative audit scenario:
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://fastgpt:audit_pass@localhost:27017/ads_audit?authSource=admin | Adapts to storage requirements for unstructured data such as ad creatives and audit records, specifies an authentication source to ensure access security, and matches the high-concurrency write demands of the ad audit scenario |
PG_URL | postgresql://audit_user:pg_pass@localhost:5432/audit_records?sslmode=disable | Stores structured data such as audit opinions and modification records, supports complex associated queries, and simplifies generation of operational report summary data |
DB_MAX_LINK | 20–30 | Matches concurrent access requirements for daily or real-time updates, prevents audit task interruptions caused by connection exhaustion, and avoids unnecessary resource waste |
REDIS_URL | redis://:redis_audit_pass@localhost:6379/0 | Caches frequently accessed compliance clause libraries and creative metadata, reduces database query pressure, and improves audit task execution efficiency |
Three common misconfigurations
- After Docker deployment, a startup error occurs indicating a database connection failure. The symptom is that
connection refusedorauthentication failedappears in the logs. The cause is that theMONGODB_URIparameter is not correctly configured, with the correct database address, port, or authentication information not specified. - Unable to connect to the local MongoDB instance via MongoDB Compass. The symptom is connection timeout or authentication failure. The cause is that the default MongoDB port 27017 is not open, or a correct access whitelist is not configured.
- Audit task execution returns an empty result. The symptom is that the interface displays no matching audit records. The cause is that the
DB_MAX_LINKconfiguration is too low, causing the connection pool to be exhausted and preventing reading of historical modification records.
How to confirm the configuration is valid
- Run
docker logs fastgptto view startup logs, and confirm there are no error messages related to database connections. - Use MongoDB Compass to connect to the configured
MONGODB_URI, and verify that ad creative metadata and audit records can be read. - Run the
redis-cli pingcommand to confirm that the Redis service responds normally, and verify that the cache configuration takes effect. - Submit a test audit task, and check whether corresponding audit records and modification logs are generated in the database.
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.