What's new in Edge Flow Manager
Edge Flow Manager (EFM) 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.
- Remote agent deployment through EFM [Technical Preview]
-
Setting up and configuring agents has been a cumbersome process. With this release, EFM now allows downloading and autoconfiguring agents directly using a generated one-liner command. Additionally, in secure environments, EFM serves as a Certificate Authority, ensuring the proper configuration of security attributes for the downloaded agents. This enhanced functionality is supported for both Java and C++ agents and accommodates Linux and Windows operating systems.
For details, see Deploying agents in CEM
- Group based IdP integration (OIDC and SAML)
-
Previously, EFM was responsible for managing group configuration information, requiring administrators to manually create groups and make assignments within EFM. With this release, EFM introduces the capability to import group and assignment information from an Identity Provider (IdP), enabling external management outside of EFM. This enhancement allows for more dynamic initial admin identities, as configuring a group as an initial admin identity becomes possible, and group assignments can be modified at a later stage.
For details, see Managing user groups by IdP.
- Diagnostic bundle
-
Authenticated users can access the Diagnostic Bundle through the /diagnostic/bundle path. This comprehensive bundle includes diagnostic information about Classes, Agents, Flows, Cluster, Endpoint Activity, Alerts, and Errors.
- EFM behind proxy - support for generated download URLs
-
When URLs are generated by EFM (for example download URLs provided to users) and a proxy exists between EFM and the user, including mappings that modify the URL path, EFM needs to be aware of these path mappings set on the proxy side. This is essential for EFM to create the correct URL that can be accessed through the proxy.
Two properties are available to manage this functionality:
efm.proxy.apiProxyPath- This property specifies the full URL where EFM API (excluding C2) can be accessed through the proxy, without a trailing slash.
efm.proxy.c2ProxyPath- This property defines the full URL where EFM C2 API can be accessed through the proxy, without a trailing slash.
- User-driven Agent Class creation
-
Admin users can now create agent classes directly from the Dashboard UI. This functionality is useful when supporting the agent deployment feature. Previously, Agent Classes were automatically generated when an agent heartbeat was received with a class not recognised by EFM. After creation, the class would remain empty until Agents began sending heartbeats with the designated class name.
- Parameter Context endpoint(s) deprecated
-
In this release, all '/parameter-contexts' endpoints previously responsible for parameter context mapping have been deprecated. The deprecated endpoints will be removed in the next major release.
These endpoints were not exposed on the user interface and could only be accessed through direct REST calls. Due to confusion surrounding their usage, the parameter context mappings have been relocated to their corresponding resources (Agent or Flow). As Agent Class level parameter contexts are not utilized and have a one-to-one mapping with Flow Parameter Contexts, the Agent Class level mapping will be completely removed in the next major release. For more information, see the Cloudera Edge Flow Manager REST API documentation .
- Additional fixes
-
For information on bug fixes, see Fixed issues.
