Changelog¶
1.14.0(2026/04/17)¶
- Added session replay image processing interface.
1.13.0(2026/04/10)¶
- Added Dataway side-channel aggregation and sampling support (#67).
1.12.3(2026/03/26)¶
- Added v2 Sinker header format to resolve issues where abnormal values in shunting headers violate HTTP standards (#68).
1.12.2(2026/03/17)¶
- Updated DataWay image SSL certificate to avoid unrecognized Openaway SSL certificate in cascading scenarios (#69).
1.12.1(2025/12/25)¶
- Fixed an issue in version 1.12.0 where Sinker shunting could not replicate requests (#66).
1.12.0(2025/12/19)¶
New Features¶
-
Optimized Sinker caching mechanism (#34).
- The new sinker caching mechanism uses hash features (16 bytes) of the request for caching, rather than caching the complete request features. It employs dual hashing to minimize hash collisions. The theoretical probability of hash collision is n/2^128, where n is the number of cached keys.
- Added TTL and capacity mechanisms to the Sinker cache to further limit memory usage: The TTL mechanism cleans inactive caches, and the capacity mechanism ensures the number of keys in the cache does not exceed a specified limit. Both TTL and capacity limits further reduce the probability of hash collisions mentioned above.
-
Added configuration to optimize Dataway HTTP header returns, reducing Dataway public network traffic (#65).
1.11.2(2025/11/25)¶
- Optimized Dataway forwarding of Kodo HTTP requests (#64).
1.11.1(2025/11/15)¶
- Fixed the issue of
__internal__token being invalid (#63).
1.11.0(2025/11/12)¶
New Features¶
- Upgraded DataWay base image to Ubuntu 22.04 (#62).
- DataWay supports blocking invalid traffic (#61).
Bug Fixes¶
- Fixed an issue where session replay and profile shunting could not replicate data to different workspaces (#59).
1.10.0(2025/09/03)¶
New Features¶
- Added Langfuse data ingestion functionality (#57).
1.9.0(2025/04/25)¶
New Features¶
- Dataway adds
X-Pkg-Idin data upload requests for data tracing (#53). - Enhanced program logging; more Kodo error codes will be passed through to Datakit (#52).
- Added API for self-pulling environment variables (#55).
- Updated disk caching code to locate
invalid argumenterrors occurring in some scenarios (#56).
1.8.0(2025/02/19)¶
New Features¶
- With Sinker mode enabled, Dataway supports simultaneously handling data reporting requests sent by clients (e.g., Datakit/Function) (#50).
1.7.0(2024/12/18)¶
New Features¶
- Added AWS Firehose ingestion endpoint (#47).
- Supports passing token via
X-Token(#43).
Optimizations¶
- Adjusted default parameters for internal recycling to optimize memory usage (#49).
- Optimized default yaml for Kubernetes deployment, adjusting its cache disk mount configuration (#48).
- Adjusted and added some internal metrics; updated Dataway default views.
1.6.2(2024/12/03)¶
Optimizations¶
- Added configuration entry for HTTP-level connections (#46).
1.6.1(2024/11/19)¶
Optimizations¶
- Added option to disable the 404 page (#44).
1.6.0(2024/09/19)¶
Optimizations¶
- Optimized environment variable configuration related to disk caching.
- Added more self-metric exposure and optimized memory usage at the HTTP forwarding layer (#39).
- Dataway supports configuring its own SNI (#42).
- Added time synchronization interface for Datakit to obtain more accurate Unix timestamps (#40).
- Sinker:
- Filtering conditions support
niljudgment, i.e., determining whether a specific field exists (#41). - Added default rule setting, where requests not matching any existing shunting rules will be directed to the workspace corresponding to this default rule (#30).
- Filtering conditions support
1.5.0(2024/07/05)¶
Optimizations¶
- Optimized installation script (#33).
Compatibility Adjustments¶
- The new version removes the feature of directly supporting Sinker configuration in host installation mode. This functionality will be supported through new methods in the future.
1.4.1(2024/06/19)¶
- Fixed missing
DW_ENABLE_TLSissue in Kubernetes installation mode. - Changed build image address.
1.4.0(2024/05/15)¶
- Added Datakit metering interface (#29).
- Fixed an issue where cache might lose data (#31).
- Supports configuring HTTP TLS certificate directly on the Dataway side (#32).
- Added more metric exposure.
1.3.9(2024/03/28)¶
- When Sink discards a request, it now returns an HTTP
406 Not Acceptableerror to facilitate troubleshooting (#82).
1.3.8(2024/01/24)¶
- Added more metric exposure.
- Significantly improved Sinker rule matching performance (#26).
1.3.7(2023/12/14)¶
- Added more metric exposure.
- Optimized disk cache cleanup strategy, adhering to the principle of consumption as soon as possible:
- Avoid proactive data discarding due to storage limits.
- Send cached data upstream as early as possible.
- Added observability for oversized request discarding (metrics/logs).
- Adjusted Dataway's own POD yaml to improve its metric and log collection.
1.3.6(2023/10/24)¶
- Added Dataway
sinkmanagement command.
1.3.5(2023/09/13)¶
- Kubernetes installation supports injecting environment variables to install Dataway.
- Newly released dataway.yaml.
1.3.4(2023/09/01)¶
- Upgraded Golang to 1.9.
- Fixed inner token data issue.
- Adjusted the following configurations in default settings:
- Default API rate limit increased to 100K.
- Default maximum Body size increased to 64MB.
- Added HTTP timeout setting (Dataway to center), default 30s.
- Added configuration to ignore TLS 509 errors.
1.3.3(2023/09/01)¶
- Fixed image packaging
curlissue.
1.3.2(2023/08/30)¶
- Added
curlcommand to the image for easy viewing of self-metrics.
1.3.1(2023/08/28)¶
- Added URL-based Sinker functionality.
1.3.0(2023/08/24)¶
- Refactored the entire Dataway implementation, adding Sinker functionality.
1.2.12(2023/08/28)¶
- Refactored CI release process to implement dual release of install script.
1.2.8(2022/09/18)¶
-
/v1/wirte interface update:
- Removed redundant /v1/write/xxx APIs, added /v1/write/:category interface.
- Data writing no longer performs line protocol decoding, but still reads the Body for signature purposes.
-
Disk cache:
- Added consumption pause strategy when sending cached data to the center fails during cache cleanup; the next cache item is not cleaned until the current cached request is successfully sent.
- Updated pbcache proto file.