Interface and Operations / System Settings

DataFlux Func supports various customizable configurations, which users can modify in the "System Settings".

Custom Website Title / Favicon / Logo

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 more aligned with the customer's specifications.

Top 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 wish to change the destination address of the documentation link, you can modify this item.

Local Func Task Record

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

Self-Monitor Data Upload

Data such as function run logs from DataFlux Func can be uploaded to the data platform.

Fill in the DataWay / OpenWay address in this item, in the following format:

DataWayDataKit

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

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

Reduce Data Storage Pressure

Generally, after configuring "Self-Monitor Data Upload", you can consider turning off "Local Func Task Record" to reduce local service pressure.

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

Custom HTTP Response Headers

Added in version 7.3.7

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

Default value is as follows:

X-Content-Type-Options: nosniff

Cross-Origin Resource Sharing (CORS)

Added in version 7.3.7

List of cross-origin Origin rules.

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

The default action upon a match is to allow cross-origin. Adding "!" at the beginning of a rule means to disallow cross-origin upon a match. If no rule is matched, cross-origin is forbidden by default, for example:

/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 the default rule
Origin Match	"http://other.site.domain"	Control for a specific origin 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 origin Origin and only for requests to specific paths Paths support * wildcard
Path Match	"/api/v1" "/api/*" "/api/v*" "/api/**"	CORS control only for requests to specific paths Paths support * wildcard
Host Match	"other.site.domain"	Control only when the Host part of the origin 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/**"	Control only when the Host part of the origin Origin matches and only for requests to specific paths Paths support * wildcard

Default configuration is as follows:

/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 them sequentially upon receiving a request and process it according to the first matched rule.

The default action upon a match is to allow access. Adding "!" at the beginning of a rule means to disallow access upon a match. If no rule is matched, access is forbidden by default, for example:

10.0.0.1
!0.0.0.0/0

Available rules and their syntax are as follows:

Rule	Example	Description
Single IP	"10.0.0.1"	Control for a specific IP address
CIDR Block	"0.0.0.0/0"	Control for a specific IP CIDR block

Default configuration is as follows:

0.0.0.0/0

Hide Script Set

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 interaction logic with the data platform are located in "Advanced Settings". Normally, please do not modify this item.

DataFlux Func ID

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

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

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