v7.0 CE Release Notes
Created:2025-08-19 Last Modified:2025-08-19
This document was translated by ChatGPT
#1. v7.0.9 [2025/06/11]
#1.1 Stable Feature
- AutoTracing
- Support collecting Unix Socket call logs (
l7_flow_log), and enable automatic tracing between TCP/UDP Socket call logs and Unix Socket call logs. - Support parsing SRV type DNS call logs, Documentation (opens new window).
- Optimize parsing of unary type gRPC calls, Documentation.
- Support collecting Unix Socket call logs (
- AutoTagging
- Support collecting change events of K8s resource definitions and ConfigMaps.
- Server
- Support MCP Server.
- Agent
- When the Agent reaches the traffic rate limit, support choosing between
droporwaitstrategies. The default behavior is drop, but it can be configured to wait to improve data sending success rate, Documentation. - Added a circuit breaker mechanism for free disk space in the Agent runtime environment, Documentation.
- Support disabling Agent's use of Swap memory, Documentation.
- Adapt to K8s CNI with identical virtual NIC MAC addresses on the same host.
- Optimization: Reduce the work done by the Agent when it is disabled.
- When the Agent reaches the traffic rate limit, support choosing between
#2. v7.0.8 [2025/05/16]
#2.1 Stable Feature
- AutoTracing
- Support parsing truncated MySQL protocol content.
- Agent
- Support compressing and sending call logs and flow logs. In test environments, call log compression ratio can reach 8:1, Documentation.
#3. v7.0.7 [2025/04/28]
#3.1 Stable Feature
- AutoTracing
- Enrich eBPF hook points for collecting file read/write events (
io_event) to improve adaptability.
- Enrich eBPF hook points for collecting file read/write events (
- AutoTagging
- Optimize the meaning of the
process_knamefield in call logs and file read/write event data, changing fromkernel thread nametosystem processname for better readability. - Aggregate processes with the same
cmdlinewithin the same cloud host or the same K8s workload into a unique gprocess to reduce redundant process information. - Optimize default values of the process matcher, Documentation.
- By default, ignore collection of process information for
sleep/sh/bash/pause/runc. - By default, collect process information and OnCPU profiling data for
Java/Python, and automatically record the gprocess name as the jar/py file name to avoid all being displayed as java/python. - By default, collect process information and OnCPU profiling data for
deepflow-*. - By default, collect process information inside containers.
- By default, ignore collection of process information for
- Optimize the meaning of the
response_statusfield in call logs (l7_flow_log).- Normal: Response code is normal.
- Client Error: Response code indicates a client-side error, e.g., HTTP 4XX.
- Server Error: Response code indicates a server-side error, e.g., HTTP 5XX.
- Timeout: If no response is collected within a certain time, the request will be marked as timed out.
- Agent
Application session merge timeoutconfiguration: DNS and TLS default 15s, other protocols default 120s, Documentation.
- Agent
- Unknown: When concurrent requests exceed the collector's cache capacity, the oldest requests will be marked as unknown.
- Agent
Maximum session aggregation entriesconfiguration: Default cache of 64K requests, Documentation.
- Agent
- Parse Failed: Response was collected but could not parse the response code due to truncation or compression.
- Agent
Payload truncationconfiguration: By default, parse the first 1024 bytes of the Payload, Documentation.
- Agent
- Optimize the meaning of the
- Agent
- Optimize memory usage of the cache for application performance metrics in the Agent by promptly clearing expired LRU entries, reducing overall memory consumption by 43% in test environments.
- Aggregate and store flow logs (
l4_flow_log) generated by LB health checks, reducing flow log storage overhead by nearly 50% in some production environments, Documentation. - Optimize the resource overhead protection mechanism when application protocol recognition fails to avoid mistakenly disabling application protocol parsing, Documentation.
#4. v7.0.6 [2025/04/15]
#4.1 Stable Feature
- AutoTracing
- Support parsing compressed MySQL calls, Documentation.
- Support parsing MySQL Login Response statements.
- Support parsing multiple DNS requests in TCP Payload.
- Agent
- Improve the merge success rate of call logs on the agent side, significantly reducing the proportion of call logs with
response_status = Unknown. In test environments, a 50% reduction in unknown proportion is observed. - Limit the bandwidth consumption of data sent by the agent, with a default allowance of 100Mbps, Documentation.
- Improve the merge success rate of call logs on the agent side, significantly reducing the proportion of call logs with
#5. v7.0.5 [2025/04/02]
#5.1 Stable Feature
- AutoTracing
- Support collection and tracing of RocketMQ protocol, Documentation.
- Support collection and tracing of Ping protocol, Documentation.
- Support collection and tracing of Dubbo protocol when using Fastjson serialization, Documentation.
#6. v7.0.4 [2025/03/18]
#6.1 Stable Feature
- Agent
- Support collecting traffic from Pod internal NICs, applicable to scenarios where Pod NIC traffic cannot be directly collected under the Root network namespace (e.g., Huawei Cloud CCE Turbo CNI (opens new window)), Documentation.
#7. v7.0.3 [2025/03/05]
N/A
#8. v7.0.2 [2025/02/11]
#8.1 Stable Feature
- AutoMetrics
- Add timeout ratio metric (
timeout_ratio) to application performance metrics (application,application_map).
- Add timeout ratio metric (
- Server
- Support terminating remote upgrades of collectors and optimize CPU resource usage of the Server during upgrades.
- Agent
- Support limiting the number of sockets used by deepflow-agent, Documentation.
#9. v7.0.1 [2025/01/16]
#9.1 Stable Feature
- AutoTracing
- For non-TCP traffic in network flow logs (
l4_flow_log), change the end status (close_type) from timeout to normal end (1).
- For non-TCP traffic in network flow logs (
#10. v7.0.0 [2025/01/02]
#10.1 Stable Feature
- AutoTracing
- Support collection and tracing of Tars protocol, Documentation.