Cloudera Docs

What's new in Cloudera Edge Management

Cloudera Edge Management (CEM) is a solution that enables you to manage, control, and monitor agents that are deployed on the edge devices in IoT implementations. You can use these agents to collect real-time data originating from the devices to create and push actionable intelligence and insights to the place of data origin.

Cloudera Edge Management 1.3.1 is a feature release that contains performance improvements, bug fixes, and new features including:
  • As a Technical Preview the DEBUG command capability is introduced. You can now issue a DEBUG command against an agent which after executing the command uploads a debug bundle with logs, agent properties, and flow configuration so that issues can be more easily investigated. This functionality will be evolved in the upcoming 1.4.0 release.

    For more information, see Using agent debug command.

  • Support is added for raw heartbeat submission to Apache Kafka from EFM. In the earlier release, only the deserialized heartbeats were sent to Apache Kafka so fields that EFM was not aware of were omitted. Now the raw heartbeat is sent to Apache Kafka.
  • The Kafka message key now contains the agent identifier.
  • Support is added for SASL_SSL integration of Apache Kafka with EFM. In the earlier release, Kafka integration was supported but only through 2-way-SSL. Now authentication is possible through SASL_SSL too using username and password.
  • From this release EFM supports the separation of C2 and UI ports. There could be use cases when different network level rules and restrictions would be applied to the UI (users) and the C2 (agents) traffic. This new enhancement supports this.

    For more information, see Using separate ports in EFM.

  • Support for sensitive property encryption is added. Now it is possible to encrypt one or more properties so that EFM can decrypt those at startup using the provided key. Small utility script is included to help the encryption.

    For more information, see Encrypt sensitive properties.

  • Enhancements are made around observability, namely the health and info endpoints are enhanced along with additional metrics exposed.
  • Starting with EFM 1.3.0, support for NiFi Registry integration is deprecated, and the NiFi Registry integration feature will be removed from the future versions of EFM.
    NiFi Registry integration was originally supported for the following use cases:
    • Designing flows outside of EFM
    • Saving a backup copy of flows designed from EFM

    However, both use cases are better supported without using NiFi Registry. Also, without using NiFi Registry, EFM gains the ability to import and export flows in many formats, which improves flow design portability. For restoring flows from backups, EFM database backup option offers a better experience compared to NiFi Registry backup option. Because, when reading from NiFi Registry to EFM, key metadata is lost and cannot be fully recovered. For this reason, in order to accelerate the EFM roadmap and offer you the best capabilities and experience, Cloudera is deprecating and eventually removing the ability to write a copy of flows to NiFi Registry. Starting with EFM 1.3.0, Cloudera recommends that if you have enabled NiFi Registry integration, then disable it by setting the efm.nifi.registry.enabled property to false, in the efm.properties file, so that upgrades to future versions become more seamless.

For more information on bug fixes, see Fixed issues.