To help us make our products always better, we automatically collect data regarding usage statistics on running 4D Server applications. Collected data is completely anonymous and data is transferred with no impact on the user experience.
This page explains:
- what information is collected,
- where information is stored and when it is sent to 4D,
- how to disable automatic data collection in client/server built applications.
Data is collected during the following events:
- database startup,
- database closure,
- web server startup,
- php execution,
- client connection,
- data collection sending.
Some data is also collected at regular intervals.
Collected at database startup
|Name, type, and speed of the processor
|Total number of cores
|Volume of memory storage (in bytes) available on the machine
|Operating system version and build number
|True if the application is running in headless mode
|Version number of the 4D application
|Build number of the 4D application
|Commercial name and description of product licenses
|True if 4D is emulated through Rosetta on macOS, False otherwise (not emulated or on Windows).
|Unique ID of the 4D Server
|Text (hashed string)
|Unique id associated to the database (Polynomial Rolling hash of the database name)
|Data file size in bytes
|Index size in bytes
|Cache size in bytes
|True if legacy network layer used for the application server
|True if the database uses the QUIC network layer
|True if client/server connections are encrypted
|True if the data file is encrypted
|True if the application is compiled
|True if the application is merged with 4D Volume Desktop
|True if the application is a project
|Information on mobile sessions
Collected at web server startup and data collection sending
|"started":true if the web server is starting or started
Collected at regular intervals
|Maximum number of simultaneous web processes
|Maximum use of physical memory
|Maximum use of virtual memory
Collected at data collection sending
|Time elapsed (in seconds) since local 4D database was opened
|Number of bytes read from cache
|Number of bytes missed from cache
|Number of reads in the cache
|Number of reads missed in the cache
|Number of bytes read in the data file
|Number of bytes written in the data file
|Number of reads in the data file
|Number of writes in the data file
|Number of bytes read in the index file
|Number of bytes written in the index file
|Number of reads in the index file
|Number of writes in the index file
Collected at database closure and data collection sending
|Number of hits on the web server during the data collection
|Number of hits on the REST server during the data collection
|Bytes received by the web server during the data collection
|Bytes sent by the web server during the data collection
|Number of Qodly webforms
Collected every time PHP execute is called
|Number of calls to
|True if the client performs a call to
PHP execute and uses its own version of php
Collected at client connection
|Maximum number of 4D Client connections to the server
|Client OS without the build number (in parenthesis) and number of clients using it
Where is it stored and sent?
Collected data is written in a text file (JSON format) per database when 4D Server quits. The file is stored inside the active 4D folder, i.e.:
- on Windows:
- on macOS:
Once a week, the file is automatically sent over the network to 4D. The file is then deleted from the active 4D folder.
If the file could not be sent for some reason, it is nevertheless deleted and no error message is displayed on the 4D Server side.
The file is sent to the following server address:
https://dcollector.4d.com (ip: 188.8.131.52).
Disabling data collection in client/server built applications
You can disable the automatic data collection in client/server built applications.
To disable the collection, pass the value False to the
ServerDataCollection key in the
buildApp.4DSettings file, used to build the client/server application.