diff --git a/en_US/getting-started/assets/message_queque.png b/en_US/getting-started/assets/message_queque.png new file mode 100644 index 000000000..de24d5517 Binary files /dev/null and b/en_US/getting-started/assets/message_queque.png differ diff --git a/en_US/getting-started/new-features.md b/en_US/getting-started/new-features.md index fcf18907f..010682b11 100644 --- a/en_US/getting-started/new-features.md +++ b/en_US/getting-started/new-features.md @@ -6,82 +6,111 @@ description: This section lists the new features introduced in EMQX 5.2 and late This page highlights major new features supported in the current release. Note that it does not list every feature provided by EMQX. -## Cluster Linking +## EMQX 6.0.0 (Latest) -Cluster Linking enables seamless, secure, and efficient message sharing between geographically distributed EMQX clusters. Unlike traditional MQTT bridges, which forward all messages and often require topic prefixes to prevent feedback loops, Cluster Linking transfers only relevant messages based on active subscriptions, minimizing bandwidth use, reducing latency, and increasing scalability. +### Message Queue -The configuration and management of Cluster Linking are designed to be simple and flexible. You can create, modify, and monitor cluster links directly from the EMQX Dashboard, configuration file, or through REST APIs. EMQX also provides visual status indicators and link statistics for real-time visibility. +Message Queue unifies reliable real-time MQTT publish/subscribe with asynchronous message queueing within EMQX, without relying on external queuing services. -To get started with the Cluster Linking, see [Quick Start with Cluster Linking](../cluster-linking/quick-start.md). +Unlike traditional MQTT, which depends on subscriber availability, Message Queues decouple publishers and subscribers by buffering messages on the server. Messages matching a specified topic filter are stored persistently and can be consumed later using a special topic format: `$q/{topic_filter}`. This ensures reliable message delivery, even when clients are offline or the network is unstable. -![cluster_linking_feature](./assets/cluster_linking_feature.png) +message_queue -## Schema Validation +This feature enables MQTT to handle both real-time and delayed workloads, simplifying IoT system architecture by removing the need for external queuing systems like Kafka or RabbitMQ. It’s ideal for scenarios where message durability, reliable delivery, and offline buffering are critical. -[Schema Validation](../data-integration/schema-validation.md) ensures that only messages conforming to predefined formats are processed or delivered. EMQX supports JSON Schema, Protobuf, Avro, and rule engine SQL syntax for validation. Based on the outcome, users can configure actions such as dropping messages, disconnecting clients, or triggering rule engine events for failed validations. +#### Feature Highlights +- **Unified Messaging Model**: Combines lightweight MQTT with enterprise-grade queuing in a single system. +- **Offline Storage**: Messages are retained even when subscribers are disconnected. +- **Last-Value Retention**: Optionally keep only the latest message per key (e.g., device ID), perfect for fast-changing data like sensor readings. +- **Flexible Dispatch Strategies**: Choose from Random, Round Robin, or Least Inflight Subscriber to distribute messages efficiently. +- **Guaranteed Delivery**: Supports persistent storage and QoS 1 delivery to ensure no data is lost. -## Message Transformation +Learn more in the [Message Queue documentation](../message-queue/message-queue-concept.md). -[Message Transformation](../data-integration/message-transformation.md) allows users to define transformation pipelines that decode, modify, and re-encode messages before delivery or further processing. The system supports nested transformations, multiple encoders/decoders, and dynamic value assignments using [Variform expressions](../configuration/configuration.md#variform-expressions). +### Multi-Tenancy with Namespaced Roles -## Expanded Support in Data Integration +EMQX 6.0.0 introduces namespaced roles to enhance [multi-tenancy](../multi-tenancy/namespace-overview.md) and access control across large-scale IoT deployments. With this feature, users are assigned to specific namespaces, isolated environments where they can manage their own resources such as Rules, Connectors, and Actions, without accessing or impacting other tenants. -Recent versions of EMQX have significantly enhanced the data integration capabilities. New data integrations supported in recent versions include, but are not limited to, the following: +Namespaced roles support fine-grained permissions such as Administrator and Viewer, and can be managed through the Dashboard, API, or CLI, making it easier to delegate responsibilities while ensuring secure isolation between teams, departments, or customers. -- **[Snowflake](../data-integration/snowflake.md)**: Writes the processed data to the Snowflake Stage and loads it into a Snowflake table. Safely store IoT data in Snowflake for long-term archival and leverage Snowflake's data warehousing and analytics capabilities to perform real-time or batch analysis. -- **[Azure Blob Storage](../data-integration/azure-blob-storage.md)**: Seamlessly integrates EMQX with Microsoft Azure’s scalable object storage service. Ideal for archiving massive volumes of IoT telemetry and event data, it supports storing both structured and unstructured data in a durable, cost-effective way, similar to AWS S3. -- **[Datalayers](../data-integration/data-bridge-datalayers.md)**: Datalayers is a distributed edge-cloud database platform designed for Industrial IoT, Internet of Vehicles (IoV), and energy systems. Through the integration with EMQX, users can ingest real-time data into Datalayers for time-series storage, key-value caching, and perform analytics. +#### Feature Highlights +- **Secure Isolation**: Users can only access and manage resources within their assigned namespace (e.g., `ns:team_a::administrator`). +- **Granular Access Control**: Namespaced users have full access to namespace-specific resources, but cluster-level settings remain read-only unless granted global admin rights. +- **Simplified Operations**: Roles can be created and assigned easily during user creation. +- **Scalability for Enterprises**: Ideal for organizations offering multi-tenant MQTT services or managing internal business units with separate responsibilities. -## Enhanced Security +#### Additional Enhancements +- **Improved Observability**: Dashboard views are filtered by namespace for better focus. +- **Optimized Session Tracking**: Namespaced session counts now refresh on demand (under 1,000 sessions) or every 5 seconds otherwise, ensuring better performance and accuracy. -In recent versions, EMQX supports more authentication and authorization methods, providing more flexible and fine-grained access control capabilities. Newly supported features include: +For detailed instructions, see [Create a User with a Namespaced Role](../dashboard/system.md#create-a-user-with-a-namespaced-role). -- **[LDAP Integration](../access-control/authn/ldap.md)**: Authenticate users against an external LDAP directory, supporting enterprise-grade user management. -- **[REST API-Based MQTT 5.0 SCRAM Authentication](../access-control/authn/scram_restapi.md)**: Leverage a RESTful API for SCRAM-based authentication in compliance with MQTT 5.0 standards. -- **[Kerberos Authentication](../access-control/authn/kerberos.md)**: Integrate with Kerberos-based SSO systems for secure, centralized user authentication. -- **[Client-Info Authentication](../access-control/authn/cinfo.md)**: Allow flexible access control based on client metadata like IP, device ID, or username. +### Optimized Durable Storage -## OpenTelemetry Integration for Metrics, Logs, and Traces +EMQX 6.0.0 delivers significant improvements to durable storage, enhancing performance and scalability for high-throughput IoT workloads. By decoupling session data from other broker metadata, EMQX now consumes less RAM and achieves better storage efficiency, allowing more connections per node. -EMQX now supports OpenTelemetry, making it easier to monitor and troubleshoot your MQTT systems. +#### Optimized RocksDB Parameters -**Key Features:** +New configuration options give precise control over memory and performance: -- **Metrics**: Exports real-time metrics to OpenTelemetry Collector, then view them in tools like Prometheus and Grafana. -- **Logs**: Sends structured logs with rich context (like trace IDs) to your log system for easier debugging. -- **Tracing**: Enables distributed tracing of MQTT message flows across EMQX nodes. Useful for finding delays, routing issues, or node-specific performance bottlenecks. -- **End-to-End Tracing Mode**: Tracks full message paths and client actions. Filter by client ID, topic, or QoS. Control sampling and export rate to manage system load. +- `durable_storage.messages.rocksdb.write_buffer_size`: Controls per-shard memtable size. +- `durable_storage.messages.rocksdb.cache_size`: Sets block cache size per shard. +- `durable_storage.messages.rocksdb.max_open_files`: Limits file descriptors per shard. +- `durable_storage.messages.layout.wildcard_thresholds`: Optimizes wildcard handling in storage layout. -OpenTelemetry helps you get full visibility into EMQX performance and message flows using open, standard tools. Refer to [Integrate with OpenTelemetry](../observability/opentelemetry/opentelemetry.md) for details. +#### Additional Enhancements -## New Protocol Gateways +- **Efficient Serialization**: The default serialization format has changed to ASN.1, reducing storage size and improving processing speed. +- **Faster Access & Lower Overhead**: Improved storage layout leads to quicker message retrieval and reduced disk and memory overhead. -EMQX introduced several new protocol gateways to support industry-specific messaging standards, enabling direct integration with vertical systems in transportation, energy, and electric mobility. +These enhancements make EMQX more capable of handling large-scale, persistent MQTT workloads with consistent performance. -- **[OCPP Gateway](../gateway/ocpp.md)**: Provides native support for the Open Charge Point Protocol (OCPP) 1.6, allowing EMQX to connect directly with EV charging stations and convert OCPP messages into MQTT for unified communication. -- **[JT/T 808 Gateway](../gateway/jt808.md)** Implements the JT/T 808 protocol for vehicle telematics, enabling EMQX to receive binary messages from GPS terminals and onboard units and forward them as hex-encoded payloads in MQTT messages for downstream decoding and analysis. -- **[GB/T 32960 Gateway](../gateway/gbt32960.md)**: Enables EMQX to receive, decode, and forward structured diagnostic and telemetry data from new energy vehicles via MQTT, based on the GB/T 32960 protocol. +### Expanded Support in Data Integration -These gateways make it easier to bring industry-standard protocols into an MQTT-based data platform, supporting scenarios like smart charging, fleet monitoring, and EV data reporting. +EMQX 6.0.0 continues to strengthen its data integration capabilities, empowering users to seamlessly connect MQTT data with modern cloud and database ecosystems for real-time analytics, processing, and storage. -## Optimized Dashboard Experience +#### New Integrations -The EMQX Dashboard has delivered a more intuitive and powerful interface for managing your MQTT broker since version 5.8. Here are some major enhancements: +The following integrations have been newly added in EMQX 6.0.0: -**Usability Improvements** +- **[Google BigQuery](../data-integration/bigquery.md)**: Integrate MQTT data with BigQuery for large-scale data warehousing and advanced querying, enabling insights from massive IoT datasets. +- **[AWS AlloyDB](../data-integration/alloydb.md)**, **[CockroachDB](../data-integration/cockroachdb.md)**, and **[AWS Redshift](../data-integration/redshift.md)**: Stream MQTT data to these high-performance databases for real-time analytics and scalable storage. Perfect for enterprise-grade IoT analytics. -- Added pagination, searching, and status filtering to Action and Source pages, making it simpler to manage rules and integrations at scale. -- Included a one-click cluster metrics reset, speeding up diagnostics and observation of cluster changes. +#### Enhanced Integrations -**Metrics Display Enhancements** +In addition to new integrations, EMQX 6.0.0 brings powerful enhancements to existing integrations, improving performance, usability, and cloud-native compatibility: -- Optimized the `/api/v5/monitor` endpoint with concurrent RPC calls to fetch cluster-wide metrics, eliminating timeouts in large deployments. -- Added key metrics like message rates directly on the homepage, reducing navigation for critical insights. +- **Snowflake Snowpipe Streaming**: Now supports low-latency data ingestion into Snowflake tables via Snowpipe Streaming (preview feature of Snowflake), available for AWS-hosted accounts. +- **RocketMQ Action**: Adds support for `key` and `tag` templates, plus a `key_dispatch` strategy for flexible message routing and metadata enrichment. +- **S3 Tables Connector**: `access_key_id` and `secret_access_key` are now optional, with automatic retrieval from EC2 Instance Metadata Service v2 APIs in AWS-hosted environments. +- **RabbitMQ Sink**: Allows customization of Headers and Properties Templates to enhance message routing and compatibility within RabbitMQ. -**Monitoring Tools** +### Other Enhancements -Introduced a simplified webhook setup for alarm events, making it easier to automate monitoring and stay proactive. For more information, see [Integrate Webhook to Send Alarm Events](../observability/alarms.md#integrate-webhook-to-send-alarm-events). +#### Advanced LLM-Based MQTT Data Processing -## More Features +EMQX 6.0.0 enhances LLM-based data processing with support for [Google Gemini models](../flow-designer/gemini-node-quick-start.md), alongside OpenAI and Anthropic Claude. -In addition to the highlights covered above, recent EMQX updates include many other new features and enhancements. For a complete list, see the [Release Notes](../changes/changes-ee-v5.md). +#### Enhanced LDAP Support + +LDAP authorization now supports extended ACL rules in JSON format, and LDAP authentication can fetch ACL rules directly from LDAP with client-side caching. + +#### Improved Tracing + +Configurable limits for maximum traces (`trace.max_traces`) and trace file sizes (`trace.max_file_size`). After `max_file_size` is reached, the trace log will rotate to a new file instead of halting. + +#### Cluster Management + +New `cluster.description` configuration option allows users to set and display custom cluster descriptions in the EMQX Dashboard. For how to add the cluster description on the Dashboard, see [Dashboard -> Management -> Cluster Settings](../dashboard/cluster_settings.md#cluster). + +### More Features + +In addition to the highlights covered above, recent EMQX updates include many other new features and enhancements. For a complete list, see the [Release Notes](../changes/changes-ee-v6.md). + +### Breaking Changes + +For complete information about what's deprecated and breaking changes, see [Incompatible Changes between EMQX 5.x and EMQX 6.0](../changes/breaking-changes-6.0.md). + +## EMQX 5.x Series + +For a complete list of features and updates in EMQX 5.x, please refer to: [EMQX 5.10 Documentation – What's New](https://docs.emqx.com/en/emqx/5.10/getting-started/new-features.html). diff --git a/zh_CN/getting-started/assets/message_queque.png b/zh_CN/getting-started/assets/message_queque.png new file mode 100644 index 000000000..de24d5517 Binary files /dev/null and b/zh_CN/getting-started/assets/message_queque.png differ diff --git a/zh_CN/getting-started/new-features.md b/zh_CN/getting-started/new-features.md index 6753bffd3..62396b760 100644 --- a/zh_CN/getting-started/new-features.md +++ b/zh_CN/getting-started/new-features.md @@ -2,82 +2,119 @@ 本页重点展示当前版本支持的主要新功能，不涵盖 EMQX 提供的全部功能。 -## 集群连接 +## EMQX 6.0.0（最新版本） -集群连接可以实现地理分散的 EMQX 集群之间安全、高效、透明的消息共享。与传统 MQTT 桥接需转发全部消息并使用主题前缀防止循环相比，集群连接仅传输有订阅需求的消息，节省带宽、降低延迟、提升扩展性。 +### 消息队列 -集群连接的配置与管理操作简便，可通过 EMQX Dashboard、配置文件或 REST API 创建、修改和监控连接，且提供实时状态指示和链路统计信息。 +EMQX 6.0.0 引入了原生**消息队列**功能，将可靠的实时 MQTT 发布/订阅与异步消息队列功能集成在同一平台中，无需依赖任何外部队列服务。 -开始使用集群连接，请参阅： [集群连接快速开始](../cluster-linking/quick-start.md)。 +与传统 MQTT 依赖订阅者在线不同，消息队列通过在服务器端缓存消息，实现发布者与订阅者的解耦。匹配特定主题过滤器（Topic Filter）的消息会被持久化存储，并可通过特殊的主题格式 `$q/{topic_filter}` 进行消费。这确保了即使客户端离线或网络不稳定，也能可靠地传递消息。 -![cluster_linking_feature](./assets/cluster_linking_feature.png) +message_queue -## Schema 验证 +该功能使 MQTT 同时支持实时与延迟消息处理，简化了物联网系统架构，无需再引入 Kafka 或 RabbitMQ 等外部队列系统。它特别适用于对消息持久性、可靠传递和离线缓存有严格要求的场景。 -[Schema 验证](../data-integration/schema-validation.md)功能可确保仅符合预定义格式的消息被处理或投递。EMQX 支持使用 JSON Schema、Protobuf、Avro 及规则引擎 SQL 语法进行格式校验。针对校验失败的消息，用户可以配置自动丢弃、断开客户端连接或触发规则引擎等动作。 +#### 功能亮点 -## 消息转换 +- **融合的消息处理模型**：在单一系统中将轻量级 MQTT 与企业级消息队列相结合。 +- **离线消息存储**：即使订阅者断开连接，消息也会被保留。 +- **最后值保留**：可选启用“最后值语义”功能，启用后，EMQX 会基于指定的队列键（如设备 ID）保留每个键的最新消息。该特性非常适用于传感器读数等快速变化的数据场景，旧消息可被安全丢弃。 +- **灵活的分发策略**：支持随机（Random）、轮询（Round Robin）和最少未完成订阅者（Least Inflight Subscriber）等分发方式，实现高效消息分配。 +- **可靠消息投递**：支持持久化存储与 QoS 1 级消息投递，确保数据无丢失。 -[消息转换](../data-integration/message-transformation.md)允许用户定义消息转换管道，在投递前对消息进行解码、修改和重新编码。系统支持嵌套转换、多个编码器/解码器，并可通过 [Variform 表达式](../configuration/configuration.md#variform-表达式)实现动态字段赋值。 +详细信息请参阅 [Message Queue 文档](../message-queue/message-queue-concept.md)。 -## 数据集成功能扩展 +### 命名空间角色的多租户支持 -近期版本的 EMQX 显著增强了数据集成功能，新增了多种数据集成类型，包括但不限于： +EMQX 6.0.0 引入了**命名空间角色**，以增强[多租户](../multi-tenancy/namespace-overview.md)和访问控制能力，特别适用于大规模物联网部署。 -- **[Snowflake](../data-integration/snowflake.md)**：将处理后的数据写入 Snowflake Stage 并加载至 Snowflake 表中。可安全地进行长期归档，并利用其数据仓库与分析能力实现实时或批量分析。 -- **[Azure Blob Storage](../data-integration/azure-blob-storage.md)**：与 Microsoft Azure 的可扩展对象存储服务集成，支持结构化与非结构化数据的持久化存储，适用于大规模 IoT 数据归档，功能类似于 AWS S3。 -- **[Datalayers](../data-integration/data-bridge-datalayers.md)**：Datalayers 是面向工业物联网、车联网与能源行业的边云协同分布式数据库平台。通过与 EMQX 的集成，用户可将实时数据写入 Datalayers，实现时序存储、键值缓存及边缘计算分析。 +通过该功能，用户可被分配至特定命名空间，每个命名空间都是一个隔离的环境，用户仅能管理自己命名空间内的资源，如规则、连接器和动作，而不会访问或影响其他租户。 -## 安全性增强 +命名空间角色支持细粒度权限控制（如管理员、查看者），并可通过 Dashboard、API 或 CLI 进行管理，使管理员能够轻松分配职责，同时确保团队、部门或客户之间的安全隔离。 -EMQX 在近期版本中新增了多种认证与授权机制，提供更灵活、细粒度的访问控制能力。新增支持的功能包括： +#### 功能亮点 -- **[使用 LDAP 进行密码认证](../access-control/authn/ldap.md)**：通过外部 LDAP 目录验证用户，支持企业级用户管理。 -- **[基于 REST API 的 MQTT 5.0 SCRAM 认证](../access-control/authn/scram_restapi.md)**：支持符合 MQTT 5.0 标准的 SCRAM 认证方式，基于 RESTful API 实现。 -- **[Kerberos 认证](../access-control/authn/kerberos.md)**：集成 Kerberos 单点登录系统，实现安全的集中式用户认证。 -- **[Client-Info 认证](../access-control/authn/cinfo.md)**：基于客户端元信息（如 IP 地址、设备 ID 或用户名）实现灵活的访问控制。 +- **安全隔离**：用户仅能访问其所属命名空间内的资源，例如 `ns:team_a::administrator`。 +- **精细化访问控制**：命名空间用户可完全管理其命名空间资源，但集群级设置仅可查看，除非被授予全局管理员权限。 +- **简化运维**：在创建用户时即可轻松创建并分配命名空间角色。 +- **企业级可扩展性**：非常适合为多个租户提供 MQTT 服务的组织，或管理多个业务单元的企业环境。 -## OpenTelemetry 集成：指标、日志与追踪 +#### 其他增强 -EMQX 现已全面支持 OpenTelemetry，使用户可以更轻松地监控和排查 MQTT 系统中的问题。 +- **改进可观测性**：Dashboard 视图现在会根据命名空间自动过滤，更加聚焦。 +- **优化会话统计**：当连接数少于 1,000 时，会话计数实时刷新；否则每 5 秒刷新一次，以提高性能与准确性。 -**主要功能：** +详细操作请参阅 [创建具有命名空间角色的用户](../dashboard/system.md#创建具有命名空间角色的用户)。 -- **指标监控**：将实时指标数据导出至 OpenTelemetry Collector，并可通过 Prometheus、Grafana 等工具进行可视化。 -- **日志采集**：发送结构化日志，包含丰富上下文信息（如 Trace ID），方便调试与故障定位。 -- **追踪**：支持在 EMQX 节点间对 MQTT 消息流进行分布式追踪，有助于发现延迟、路由问题或特定节点的性能瓶颈。 -- **端到端追踪模式**：可完整追踪消息路径和客户端操作，支持按客户端 ID、主题或 QoS 等维度过滤，用户可自定义采样率与导出频率以平衡系统负载。 +### 持久化存储优化 -借助 OpenTelemetry，您可以通过开放的标准工具全面掌握 EMQX 的性能与消息流动情况。详细信息请参阅 [OpenTelemetry 集成](../observability/opentelemetry/opentelemetry.md)。 +EMQX 6.0.0 在持久化存储方面进行了显著优化，提升了性能与可扩展性，更好地支持高吞吐量的物联网工作负载。通过将会话数据与其他消息服务器的元数据解耦，EMQX 显著降低了内存使用量并提高了存储效率，从而在相同硬件条件下支持更多连接。 -## 新增协议网关 +#### RocksDB 参数优化 -EMQX 在 5.2 至 5.8 版本中新增了多种行业协议网关，支持交通、能源与电动汽车等垂直领域的系统接入，帮助用户将行业标准协议的数据快速接入基于 MQTT 的平台。 +新增的配置项允许用户更精细地控制内存与性能： -- **[OCPP 协议网关](../gateway/ocpp.md)**：支持 OCPP 1.6 协议，EMQX 可直接连接电动汽车充电桩，将 OCPP 消息转换为 MQTT 消息，实现统一通信管理。 -- **[JT/T 808 协议网关](../gateway/jt808.md)**：支持 JT/T 808 车载终端通信协议，EMQX 可接收来自 GPS 终端与车载设备的二进制消息，并以十六进制编码形式通过 MQTT 发布供下游系统解析。 -- **[GB/T 32960 协议网关](../gateway/gbt32960.md)**：基于 GB/T 32960 协议，使 EMQX 能够接收、解码并通过 MQTT 转发来自新能源汽车的结构化诊断与遥测数据。 +- `durable_storage.messages.rocksdb.write_buffer_size`：控制每个分片的 RocksDB memtable 大小。 +- `durable_storage.messages.rocksdb.cache_size`：设置每个分片的 RocksDB 块大小。 +- `durable_storage.messages.rocksdb.max_open_files`：限制每个分片 RocksDB 使用的文件描述符数量。 +- `durable_storage.messages.layout.wildcard_thresholds`：允许为 `wildcard_optimized_v2` 存储布局调整通配符阈值。 -这些网关简化了行业协议到 MQTT 的接入流程，广泛应用于智能充电、车队监控与新能源汽车数据上报等场景。 +#### 其他增强 -## Dashboard 优化 +- **高效序列化**：默认消息序列化格式改为 ASN.1，减小存储体积并提升处理速度。 +- **更快访问与更低开销**：优化后的存储布局使消息检索更快，同时降低磁盘与内存开销。 -自 5.8 版本起，EMQX Dashboard 引入了更直观、功能更强的管理界面，提升了日常运维与监控体验。 +这些改进使 EMQX 更加适用于需要稳定性能的大规模持久化 MQTT 负载场景。 -**易用性提升** +### 扩展的数据集成支持 -- 为规则引擎的动作与 Source 页面新增分页、搜索与状态筛选功能，方便大规模集成管理。 -- 增加“一键重置集群指标”功能，便于快速诊断并观察集群状态变化。 +EMQX 6.0.0 进一步增强了数据集成功能，支持与各类主流云服务和高性能数据库生态系统无缝集成，实现实时分析、处理与存储。 -**指标展示增强** +#### 新增集成 -- 对 `/api/v5/monitor` 接口进行优化，使用并发 RPC 拉取全集群指标，避免在大规模部署下出现超时。 -- 在首页新增核心指标（如消息速率），方便快速获取关键数据。 +以下数据集成在 EMQX 6.0.0 中全新支持： -**监控工具集成** +- **[Google BigQuery](../data-integration/bigquery.md)**：将 MQTT 数据流式传输至 BigQuery，实现大规模数据仓储与高级查询，从海量物联网数据中获取洞察。 +- **[AWS AlloyDB](../data-integration/alloydb.md)**、**[CockroachDB](../data-integration/cockroachdb.md)** 和 **[AWS Redshift](../data-integration/redshift.md)**：将 MQTT 数据流式发送至这些高性能分布式数据库，用于实时分析与可扩展存储，非常适合企业级物联网分析场景。 -- 提供 Webhook 集成功能，用于发送告警事件，便于实现自动化监控与异常响应。参见 [Webhook 告警集成配置](../observability/alarms.md#通过-webhook-集成发送告警事件通知)。 +#### 增强的集成能力 -## 更多功能 +除了新增集成外，EMQX 6.0.0 还对现有集成进行了性能、可用性与云原生兼容性优化： + +- **Snowflake Snowpipe Streaming**：现支持通过 Snowpipe Streaming（Snowflake 的预览版功能）将数据低延迟写入 Snowflake 表，适用于 AWS 托管账户。 +- **RocketMQ 动作**：新增 `key` 与 `tag` 模板字段，并提供 `key_dispatch` 消息分发策略，实现更灵活的消息路由与元数据管理。 +- **S3 Tables 连接器**：`access_key_id` 与 `secret_access_key` 参数现为可选项，EMQX 可自动通过 AWS EC2 Instance Metadata Service v2 获取凭证，实现无缝集成。 +- **RabbitMQ Sink**：支持自定义消息 Headers 与 Properties 模板，提升消息在 RabbitMQ 中的消息路由能力和兼容性。 + +### 其他增强功能 + +#### 基于 LLM 的高级 MQTT 数据处理 + +EMQX 6.0.0 在基于大语言模型（LLM）的数据处理方面进一步增强，现已支持 [Google Gemini 模型](../flow-designer/gemini-node-quick-start.md)，并兼容 OpenAI 与 Anthropic Claude。 + +#### 增强的 LDAP 支持 + +LDAP 授权现支持 JSON 格式的扩展 ACL 规则，LDAP 认证还可直接从 LDAP 拉取 ACL 规则并支持客户端缓存。 + +#### 日志追踪功能改进 + +新增可配置项： +- `trace.max_traces`：限制最大追踪数量； +- `trace.max_file_size`：限制追踪文件大小，当达到最大值后自动轮转新文件，而非停止记录。 + +#### 集群管理 + +新增配置项 `cluster.description`，允许用户在 Dashboard 中为集群设置并显示自定义描述。详细步骤请参阅 [EMQX Dashboard -> 管理 -> 集群配置](../dashboard/cluster_settings.md#集群)。 + +### 更多功能 + +除了上述功能，EMQX 最近的版本还包含诸多增强和优化。完整详情请参阅：[版本更新日志](../changes/changes-ee-v6.md)。 + +### 不兼容变更 + +有关弃用项与不兼容变更的完整信息，请参阅 [EMQX 5.x 与 6.0 不兼容变更](../changes/breaking-changes-6.0.md)。 + +## EMQX 5.x 系列 + +有关 EMQX 5.x 的全新功能，请参阅 EMQX 企业版 v5 版本的[全新功能](https://docs.emqx.com/zh/emqx/v5.10/getting-started/new-features.html)。 -除了上述功能，EMQX 最近的版本还包含诸多增强和优化。完整详情请参阅：[版本更新日志](https://github.com/emqx/emqx-docs/blob/6f1b5b885bb9a82475d567433a0b477a0ef34d0b/zh_CN/changes/changes-ee-v5.md)。