Skip to content

Interface and Operations / System Settings

DataFlux Func supports various customization configurations. Users can modify these configuration items in "System Settings".

system-setting.png

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

When you use DataFlux Func to implement functional requirements and deliver them to customers, you can modify these configuration items to make DataFlux Func better match the customer's specifications.

Top Notice Bar

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

notice-bar.png

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

Local Function Task Records

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

Self-Monitoring Data Upload

Information such as function execution logs from DataFlux Func can be uploaded to the data platform.

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

Text Only
1
http://openway.ip-or-domain?token=tkn_xxxxx
Text Only
1
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 local service pressure.

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

Custom HTTP Response Headers

Added in version 7.3.7

After configuration, all HTTP responses from DataFlux Func will include the specified content in their headers.

The default value is as follows:

Default Value
1
X-Content-Type-Options: nosniff

Cross-Origin Resource Sharing (CORS)

Added 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 it according to the first matching rule.

By default, a match results in allowing cross-origin. Adding "!" at the beginning of a rule indicates that a match results in disallowing cross-origin. If no rule matches, the default is to forbid cross-origin. For example:

Allow cross-origin for all APIs starting with /api/v1/func-api/, disallow others
1
2
/api/v1/func-api/**
!*

Available rules and their syntax are as follows:

Rule Example Description
Any "*" A rule that always matches, can be placed last as a default rule.
Origin Match "http://other.site.domain" Control for a specific request 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/**"		 Control for a specific request Origin and only when requesting specific paths.
Paths support * wildcard.
Path Match "/api/v1"
"/api/*"
"/api/v*"
"/api/**"		 CORS control only when requesting specific paths.
Paths support * wildcard.
Host Match "other.site.domain" Control only when the Host part of the request Origin matches.
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/**"		 Control only when the Host part of the request Origin matches and only when requesting specific paths.
Paths support * wildcard.

The default configuration is as follows:

Default Value
1
2
3
4
5
6
7
8
9
/api/v1/func-api/**
/api/v1/cron/*
/api/v1/func-api-list
/api/v1/func/integration/sign-in
/api/v1/fs/**
/api/v1/sync/**
/api/v1/async/**
/api/v1/al/**
/api/v1/bat/**

IP Address Filter

Added in version 7.3.7

IP address filtering rules.

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

By default, a match results in allowing access. Adding "!" at the beginning of a rule indicates that a match results in disallowing access. If no rule matches, the default is to forbid access. For example:

Allow 10.0.0.1 to access, disallow others
1
2
10.0.0.1
!0.0.0.0/0

Available rules and their syntax are as follows:

Rule Example Description
Single IP Address "10.0.0.1" Control for a specific single IP address.
IP Range "0.0.0.0/0" Control for a specific IP address range.

The default configuration is as follows:

Default Value
1
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 involving the underlying logic of DataFlux Func and its interaction logic with the data platform are located in "Advanced Settings". Under normal circumstances, please do not modify these items.

DataFlux Func ID

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

If a user's DataFlux Func is deployed via a full clone (e.g., using an Alibaba Cloud image), the data platform will be unable to distinguish between the old and new DataFlux Func instances.

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