-
Notifications
You must be signed in to change notification settings - Fork 69
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
59ec8a8
commit aed3620
Showing
4 changed files
with
150 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,54 @@ | ||
| ## Introduction | ||
|
|
||
| In industrial automation, the seamless exchange of data between disparate systems is paramount. Industrial gateway solutions are the key to this exchange, facilitating communication between different devices, protocols, and applications within industrial environments. By translating data formats and protocols, they enable seamless interoperability, thereby enhancing operational efficiency, productivity, and decision-making. | ||
|
|
||
| Among the myriad options available, PLC4X, Kepware, and Monkot Server stand out as key players in the field. In this blog, we delve into these industrial gateway solutions to help you make informed decisions for your automation needs. | ||
|
|
||
| ## PLC4X | ||
|
|
||
| PLC4X is a suite of libraries designed to communicate with industrial programmable logic controllers (PLCs) using a variety of protocols, all accessed through a common API. To use PLC4X, you need to integrate it into your application. Its main feature is that it provides a common API that allows applications to easily connect to different devices through consistent interfaces. However, it's important to note that PLC4X functions primarily as a library module for applications and does not include built-in data filtering and processing capabilities for your application's specific requirements. | ||
|
|
||
| ## Kepware | ||
|
|
||
| Kepware has established itself as a top-tier provider of OPC servers, known for its reliable gateway solutions designed for diverse industrial needs. With the introduction of Kepware+, the company has elevated its offerings by enabling remote monitoring and configuration across the entire enterprise from a centralized access point. This innovation addresses the previous gap in cloud management tools for Kepware system configurations, allowing users to dedicate more time to value-adding activities. However, Kepware+ operates on a SaaS environment, requiring users to pay a subscription fee for access. | ||
|
|
||
| ## Monokot Server | ||
|
|
||
| Monokot Server, a newcomer in the industrial gateway landscape, distinguishes itself with its innovative approach and emphasis on simplicity and efficiency. Designed with a focus on ease of use and rapid deployment, Monokot Server offers plug-and-play connectivity for a variety of industrial devices and protocols. Its lightweight footprint enables seamless integration with existing infrastructure, facilitating real-time data exchange and analysis. Nevertheless, it falls short in offering Docker and Kubernetes support necessary for integration with modern cloud-native applications. | ||
|
|
||
| ## NeuronEX: A Superior Solution for Your Industrial Automation Needs | ||
|
|
||
| ### What is NeuronEX | ||
|
|
||
| [NeuronEX](https://www.emqx.com/en/products/neuronex) is a specialized software for the industrial sector, focused on collecting device data and performing intelligent analysis at the edge. Designed specifically for industrial environments, it excels at collecting industrial protocol data, integrating system data, filtering and analyzing data at the edge, integrating AI algorithms, and connecting to [IIoT platforms](https://www.emqx.com/en/blog/iiot-platform-key-components-and-5-notable-solutions). With a focus on low-latency data access management and intelligent analytics services, NeuronEX enables rapid understanding of business trends, improves operational efficiency, and promotes sustainability in industrial environments. | ||
|
|
||
| ### Why NeuronEX Stands out | ||
|
|
||
| First of all, NeuronEX goes beyond the limitations of mere protocol conversion. Unlike PLC4X, which serves primarily as a library module for integration into applications, and Kepware and Monokot Server, which act as OPC servers to facilitate protocol conversion, NeuronEX stands out as a robust streaming processing engine at the edge at scale. Its sophisticated suite of edge streaming features provides users with unparalleled capabilities for data filtering, cleansing, standardization, data normalization, analytical inspection and real-time alerting using modern streaming SQL techniques, just like Flink or Spark applications with protocol conversion capabilities running at the edge. | ||
|
|
||
|  | ||
|
|
||
| #### Designed for Cloud Technology | ||
|
|
||
| Another key difference of NeuronEX is that it is designed from the ground up for seamless integration and collaboration with cloud platforms. Unlike its competitors like Kepware and Monokot Server, which rely primarily on OPC UA/DA client/server protocols for data transfer, NeuronEX offers a variety of cloud-based protocols such as MQTT and RESTful API, and AWS IoT Core and Azure IoT connectivity modules. This key difference not only simplifies data access for cloud applications and databases, but also future-proofs industrial ecosystems against evolving technology landscapes. | ||
|
|
||
| #### Best Lightweight Design for Deployment | ||
|
|
||
| Furthermore, NeuronEX offers unmatched deployment flexibility. Its lightweight design and minimal memory requirements guarantee compatibility across various CPU architectures, making it effortless to deploy even on hardware-constrained platforms. With built-in support for Docker and Kubernetes, NeuronEX enhances its cloud-native adaptability, enabling organizations to harness state-of-the-art edge processing capabilities regardless of hardware limitations. This level of flexible deployment capability surpasses that of Monokot Server. | ||
|
|
||
| #### Better Configuration Tools | ||
|
|
||
| Kepware faces a challenge due to the absence of a centralized tool for configuring remote instances, leaving users to manage dispersed configurations. Although Kepware+ has tackled the issue of distributed configuration within organizations, it lacks robust cloud support capabilities compared to NeuronEX. NeuronEX not only offers a centralized configuration panel across the entire enterprise but also provides a comprehensive set of APIs for controlling gateway behaviors and configurations. As a result, NeuronEX emerges as the definitive solution, offering comprehensive configuration and data modeling capabilities for data collection and edge processing tailored for modern AI analytics applications. | ||
|
|
||
| ## Conclusion | ||
|
|
||
| In summary, NeuronEX transcends the limitations of its competitors to deliver a transformative approach to edge processing that redefines industry standards. With unparalleled stream processing capabilities, seamless cloud integration, flexible deployment options, and intuitive remote configuration tools, NeuronEX is a beacon of innovation in industrial automation. | ||
|
|
||
|
|
||
|
|
||
| <section class="promotion"> | ||
| <div> | ||
| Talk to an Expert | ||
| </div> | ||
| <a href="https://www.emqx.com/en/contact?product=solutions" class="button is-gradient">Contact Us →</a> | ||
| </section> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,94 @@ | ||
| 迈向未来的工业生产，需要的不仅是自动化，更是智能化。如果工业企业的管理者能够实时监测每一生产环节的设备运行状态，每一数据点位情况，洞察和优化每一步生产流程，他们将能够做出更精准的决策，提高生产效率和产品质量。 | ||
|
|
||
| 通过集成先进的指标监测工具，EMQX ECP 工业互联数据平台（下文简称“ECP”），可帮助企业实时监测和控制生产流程。 ECP 提供的指标监测功能，包括指标监控、日志管理和异常告警， 为企业提供了一个全面的数据监控和管理解决方案。 | ||
|
|
||
| 指标监控可帮助工业企业实时跟踪关键设备与生产指标，日志管理则允许企业对日志数据进行集中存储和分析，而异常告警确保企业能够在第一时间发现异常并响应潜在的系统故障和性能问题。这些功能的结合，不仅提升了生产线的透明度和可控性，还为工业生产带来了前所未有的灵活性和响应速度，确保企业在竞争激烈的市场中保持领先。 | ||
|
|
||
| 本文将详细介绍 ECP 指标监控、日志管理和异常告警这三方面的支持能力与使用方式。 | ||
|
|
||
| ## 指标监控 | ||
|
|
||
| 指标监控是确保工业互联数据平台稳定运行的关键环节。ECP 使用 Prometheus 及其 Pushgateway 组件，对[工业边缘网关软件 NeuronEX](https://www.emqx.com/zh/products/neuronex) 进行细致的指标数据收集。NeuronEX 是 EMQ 旗下部署在边缘端，专注在边端提供多源数据接入与集成、以及智能边缘流式计算，是 ECP 边缘侧的核心组件。 | ||
|
|
||
| 当 ECP 对 NeuronEX 进行纳管或托管时，系统会自动下发所需的度量指标、设定指标数据的更新频率，以及提供 Pushgateway 的连接信息。随后，NeuronEX 会根据设定的时间间隔，将指标数据定时推送至 Pushgateway，最终由 Pushgateway 将这些数据推送至 Prometheus 服务器，完成整个数据收集流程。 | ||
|
|
||
| ECP 已集成安装了 Pushgateway 和 Prometheus，简化了用户的配置工作。用户可直接在 ECP 工作台左侧菜单的**“边缘监控”**选项中查看 NeuronEX 的监控指标数据，无需进行额外设置。 | ||
|
|
||
|  | ||
|
|
||
| 指标数据主要分为三个部分：基础指标数据、NeuronEX 的详细指标数据、以及异常驱动和规则列表。 | ||
|
|
||
| - **基础指标数据**涵盖了 NeuronEX 的状态统计数据、数采模块的南北向驱动节点的统计数据、数据处理模块规则的统计数据，以及连接的设备点位数的统计数据。 | ||
| - **NeuronEX 详细指标数据**则进一步细化，展示了南向设备与北向应用各节点的连接与运行状态，以及规则处理中数据的流入流出情况。 | ||
| - **异常驱动和规则列表**则专注于展示那些处于非正常状态的数采驱动和数据处理规则。用户可以通过筛选功能更迅速地定位出现异常的边缘侧 NeuronEX 位置，并直接进入 NeuronEX 控制面板，进行必要的操作和排查。 | ||
|
|
||
| 如果需要对指标更新频率进行调整，可从“**系统设置”**下的“**通用配置”**中调整 NeuronEX 的推送时间间隔，以实现更加灵活的监控管理。 | ||
|
|
||
|  | ||
|
|
||
| ## 日志分析 | ||
|
|
||
| 在工业互联的云边协同环境中，云端和边缘端的多样化产品会产生不同格式的日志数据。为了有效管理这些数据，ECP 使用 Elasticsearch 日志服务器，它不仅统一存储日志信息，还提供聚合和可视化的查询和分析功能。以下将以边缘侧 NeuronEX 为例，具体介绍日志的使用情况。 | ||
|
|
||
| 边缘侧 NeuronEX 通过 Telegraf 将 syslog 日志数据接入 Elasticsearch。ECP 在纳管或托管 NeuronEX 时下发 Telegraf 服务地址和所需收集的日志级别信息。NeuronEX 收集的日志随后被发送至 Telegraf 的 syslog 输入插件，并通过 Elasticsearch 输出插件最终写入 Elasticsearch 日志服务器。 | ||
|
|
||
| Telegraf 已集成安装在 ECP 中，并已预配置了 syslog 输入插件信息。Elasticsearch 日志服务器需要用户自行安装。安装完成后，按以下步骤分别配置 Telegraf 输出插件和 ECP 系统配置： | ||
|
|
||
| - Telegraf 输出插件配置如下，其中： | ||
|
|
||
| - `urls` `username` `password` 分别为 Elasticsearch HTTP 服务器的访问地址、用户名、密码。 | ||
| - `index_name` 为日志在 Elasticsearch 中使用的索引名称，值必须为 `{{appname}}`。 | ||
| - `health_check_interval` 是健康检查的频率，可按需要调整。 | ||
| - `insecure_skip_verify` 是指定 Elasticsearch 开启 tls/ssl 情况下是否跳过证书链及域名检查。 | ||
| - 其他配置项说明，可参考 [Telegraf elasticsearch 插件说明](https://github.com/influxdata/telegraf/blob/master/plugins/outputs/elasticsearch/README.md)。 | ||
|
|
||
| ``` | ||
| [[outputs.elasticsearch]] | ||
| urls = [ "http://elasticsearch-server:9200" ] | ||
| username = "elastic" | ||
| password = "elastic" | ||
| index_name = "{{appname}}" | ||
| health_check_interval = "10s" | ||
| insecure_skip_verify = true | ||
| ``` | ||
|
|
||
| - ECP 的**系统设置** → **通用配置** → **日志接收器**默认关闭，在类型中选择“开启”进行启用，并选择需要的日志级别、填写 Elasticsearch 相关配置。 | ||
|
|
||
|  | ||
|
|
||
| 启用日志功能后，用户可从工作台左侧菜单的日志选项中，查看到边缘侧 NeuronEX 的实时日志，包括边缘服务名称、日志时间、日志级别和具体日志信息。通过时间及关键字段的搜索过滤功能，用户可以快速定位到目标日志，有效排查和定位具体问题。 | ||
|
|
||
| 此外，在 ECP 工作台**“边缘管理”**选项下，用户也可直接从各个 NeuronEX 边缘服务的操作栏中访问该 NeuronEX 的日志列表，进一步简化日志管理流程。 | ||
|
|
||
| ## 异常告警 | ||
|
|
||
| ECP 为管理大量边缘侧软件提供了灵活的告警机制。该机制旨在统一监控边缘侧软件的运行状况，并在出现故障或异常时及时通知用户。 | ||
|
|
||
| 一方面，ECP 的告警规则中内置了边缘侧 NeuronEX 的主要异常故障问题，用户可配置规则触发的敏感度及规则的严重级别，从而控制告警的严重程度及通知频率。 | ||
|
|
||
|  | ||
|
|
||
| 另一方面，ECP 支持细粒度的通知范围配置。用户可以为不同的 NeuronEX 配置不同的电子邮件或 Webhook 告警推送接收方式。此外，还可以针对不同告警级别设置不同的通知方式和重复告警时的沉默时效，以满足不同级别的告警通知需求。 | ||
|
|
||
|  | ||
|
|
||
| 如果用户有定制化的告警问题需要纳入 ECP 的告警通知机制，ECP 也提供了自定义告警的 REST API。用户可通过此 API 将业务中其他告警信息推送到 ECP， 并进行相应的通知。 | ||
|
|
||
|  | ||
|
|
||
| 无论用户选择何种告警推送方式或频率，ECP 都会将 NeuronEX 推送的告警信息实时地展示在告警面板中。用户可以根据时间及关键字段，对告警信息进行筛选、定位，并将已经处理完成的告警信息归档至“历史告警”。 | ||
|
|
||
|  | ||
|
|
||
| ## 总结 | ||
|
|
||
| ECP 的指标监测功能，包括指标监控、日志管理、和异常告警，都是为了帮助用户全面了解工业系统的运行情况，及时发现问题并进行故障排除，从而提升系统的可靠性、性能和安全性。这些功能也结合了工业场景中大规模数据采集、数据处理的实际需求，提供了关键的数据指标的可视化的观测能力，助力用户实现高效率的智能化生产。 | ||
|
|
||
|
|
||
|
|
||
| <section class="promotion"> | ||
| <div> | ||
| 咨询 EMQ 技术专家 | ||
| </div> | ||
| <a href="https://www.emqx.com/zh/contact?product=solutions" class="button is-gradient">联系我们 →</a> | ||
| </section> |