Data Fabric UI
Describes how to use the Data Fabric UI on a customer-managed cluster and lists some of the benefits and limitations of doing so.
The Data Fabric UI was created to be the principal user interface for the as-a-service deployment of the HPE Ezmeral Data Fabric. You can access and use the Data Fabric UI on a customer-managed cluster. However, you should understand certain benefits and limitations when using the interface in this way. The Control System is still the preferred interface for managing a customer-managed cluster.
To learn more about the differences between the as-a-service and customer-managed Data Fabric platforms, see What's New in Release 7.9.
Accessing the Data Fabric UI on a Customer-Managed Cluster
https://<host-name>:8443/app/dfui
Benefits of Using the Data Fabric UI on a Customer-Managed Cluster
- Provides GUI support for some newer Data Fabric
features that are not supported by the Control System. For example, the Data Fabric UI provides a graphical user interface for administering
OTel endpoints. You can also use
maprcli
commands to administer OTel. The Control System does not support OTel. - Makes it easy to import external NFS or S3 servers.
- Lists resource endpoints.
- Provides additional capabilities for working with topics in a stream.
Limitations of Using the Data Fabric UI on a Customer-Managed Cluster
- Can only be used with release 7.3.0 and later clusters.
- Displays limited information about ecosystem components.
- Is optimized to help you display and administer the resources of multiple fabrics (clusters) that belong to the same global namespace. If your customer-managed cluster is not a member of a global namespace, consider using the Control System. The Control System provides more visibility into the services.
- Has no support for streams or for JSON tables.
- Does not support creating or importing a fabric while connected to a customer-managed cluster. Fabric creation and import operations require a functioning global namespace. To create a fabric with a functioning global namespace, use the seed node installation method.
- Does not allow you to configure refresh intervals for metrics and the session rate.
- Does not expose system volumes and the APIServer logs.
- Is documented in another location. Instructions for using the Data Fabric UI are located in the as-a-service documentation. See the link later on this page.
Data Fabric UI Documentation
For more information about using the Data Fabric UI, see Administration in the as-a-service documentation: