Data Fabric UI

Describes how to use the Data Fabric UI on clusters and lists some of the benefits and limitations of doing so.

The Data Fabric UI is designed to be the principal user interface for the deployments of HPE Ezmeral Data Fabric that have been installed using the seed node method (formerly known as as-a-service deployments). You can access one or more clusters that have been installed by using methods other than the seed node method. 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 clusters that are not installed via a seed node.

For information on ways to install HPE Ezmeral Data Fabric, see Installation Methods.

Accessing the Data Fabric UI

To launch the Data Fabric UI, navigate to the host that is running the WebServer in the cluster. Access to the cluster typically uses HTTPS on port 8443. For example:
https://<host-name>:8443/app/dfui

Benefits of Using the Data Fabric UI on a Non-Seed Node Cluster

The Data Fabric UI:
  • Provides GUI support for some newer Data Fabric features that are not supported by the Control System. For example, 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.
    NOTE
    See Installing with a Seed Node if you wish to install a seed node fabric.
  • Facilitates the import of external data sources such as an external NFS or an external S3-compliant object store into your global namespace that contains your non-seed node cluster.
  • Lists resource endpoints.
  • Provides additional capabilities for working with topics in a stream.

Limitations of Using the Data Fabric UI on a Non-Seed Node Cluster

The Data Fabric UI:
  • 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 non-seed node 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 when logged in to the Data Fabric UI from a non-seed node cluster. Fabric creation and import operations require a functioning global namespace. To create a fabric with a functioning global namespace, use the steps provided in Installing with a Seed Node.
  • 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.

For details on performing operations related to a cluster or a fabric by using the Data Fabric UI, see Working with Multiple Fabrics Using the Data Fabric UI.