Interface and Operations / System Settings

DataFlux Func supports various custom configurations, and users can modify these configuration items in "System Settings".

Custom Site Title / Favicon / Logo

Users can modify the web page title, favicon, and logo of DataFlux Func.

When you use DataFlux Func to implement functional requirements and deliver to customers, you can modify these configuration items to make DataFlux Func more aligned with customer specifications.

Notice Bar

When you deploy multiple DataFlux Func instances, you can use the top notice bar to indicate the purpose of the current DataFlux Func.

Navigation Bar Documentation Link

If you do not want the official documentation link in the navigation bar, or you want to change the link target address, you can modify this item.

Local Function Task Records

If you do not want to record function task records locally in DataFlux Func, you can disable this item.

Self-Monitoring Data Upload

Information such as DataFlux Func function run logs can be reported to the data platform.

Fill in the DataWay / OpenWay address in this item, the format is as follows:

DataWayDataKit

http://openway.ip-or-domain?token=tkn_xxxxx

http://datakit.ip-or-domain:9529

Reduce Data Storage Pressure

Generally, after configuring "Self-Monitoring Data Upload", you can consider disabling "Local Function Task Records" to reduce the load on the local service.

For information on the reported data content, please refer to Deployment and Maintenance / Upload Self-Monitoring Data

Custom HTTP Response Headers

New in version 7.3.7

After configuration, all HTTP response headers of DataFlux Func will contain the specified content.

Default values are as follows:

X-Content-Type-Options: nosniff

Cross-Origin Resource Sharing (CORS)

New in version 7.3.7

Cross-origin Origin rule list.

One rule per line. The web service will match sequentially upon receiving a request, and process according to the first matched rule.

By default, when matched, it allows cross-origin. Adding "!" at the beginning of the rule indicates that cross-origin is not allowed when matched. If no rule matches, cross-origin is prohibited by default. For example:

/api/v1/func-api/**
!*

Available rules and their formats are as follows:

Rule	Example	Description
Any	"*"	A rule that always matches; can be placed as the last rule as the default rule
Origin Match	"http://other.site.domain"	Controls based on a specific source Origin
URL Match	"http://other.site.domain/api/v1" "http://other.site.domain/api/*" "http://other.site.domain/api/v*" "http://other.site.domain/api/**"	Controls based on a specific source Origin and only when requesting a specific path Path supports * wildcard
Path Match	"/api/v1" "/api/*" "/api/v*" "/api/**"	Controls CORS only when requesting a specific path Path supports * wildcard
Host Match	"other.site.domain"	Controls only when the Host part of the source Origin matches i.e., ignores the HTTP protocol type
Host + Path Match	"other.site.domain/api/v1" "other.site.domain/api/*" "other.site.domain/api/v*" "other.site.domain/api/**"	Controls only when the Host part of the source Origin matches and only when requesting a specific path Path supports * wildcard

Default configuration is as follows:

/api/v1/func-api/**
/api/v1/cron/*
/api/v1/func-api-list
/api/v1/auth/integration/sign-in
/api/v1/fs/**
/api/v1/sync/**
/api/v1/async/**
/api/v1/al/**
/api/v1/bat/**

IP Address Filter

New in version 7.3.7

IP address filtering rule.

One rule per line. The web service will match sequentially upon receiving a request, and process according to the first matched rule.

By default, when matched, it allows access. Adding "!" at the beginning of the rule indicates that access is not allowed when matched. If no rule matches, access is prohibited by default. For example:

10.0.0.1
!0.0.0.0/0

Available rules and their formats are as follows:

Rule	Example	Description
Single IP Address	"10.0.0.1"	Controls specified single IP address
Address Range	"0.0.0.0/0"	Controls specified IP address range

Default configuration is as follows:

0.0.0.0/0

Hidden Script Sets

By default, built-in script sets are hidden to prevent accidental operations.

If users wish to see these script sets, they can enable this configuration item.

Advanced Settings

Some configuration items related to the underlying logic of DataFlux Func and the interaction logic with data platforms are located in "Advanced Settings". Under normal circumstances, do not modify this item.

DataFlux Func ID

"DataFlux Func ID" is the unique identifier used to distinguish different DataFlux Func deployments when interacting with the data platform.

If a user's DataFlux Func is deployed through a full clone (e.g., deploying via Alibaba Cloud images), the data platform will not be able to distinguish between the old and new DataFlux Func.

In this case, modify this DataFlux Func ID to a different value.