An enterprise is an instance of ZEDEDA Cloud that is dedicated to a single ZEDEDA customer. Enterprises group users, edge nodes, and applications together to facilitate collaboration and administration. While each enterprise is associated with one ZEDEDA customer, each customer may be associated with more than one ZEDEDA enterprise.
The ZEDEDA support team creates an enterprise for every customer during their onboarding process. The credentials for the admin user account will be passed to the customer after the enterprise has been successfully created.
Enterprise CRUD operations
Read and update operations may be performed by authorized users in the ZEDEDA GUI's Enterprise Settings page, found in your profile dropdown menu.
Create and delete options may only be performed by ZEDEDA personnel.
Read
In the Settings page, you can view the following sections:
- Details: The field values such as 'Name' and 'Title' along with the description, if any, can be seen.
- Authentication Profile: More details about authentication are provided in the update operation.
Update
From your Enterprise Settings page, you can update your enterprise's identification information, GUI branding, and your authentication settings. To update your enterprise's settings, you must be an admin user.
| Input Field | Value |
| Identity |
Such as the following.
|
| Authentication Provider (*) |
Select how to authenticate new users.
|
| Authentication Type (*) | Only OAuth is supported as an authentication type currently. |
| Profile Name (*) | Select a name for the custom profile. |
| Client ID (*) | Public identifier of ZEDEDA application as registered in the authentication provider. |
| Client Secret (*) | Client secret as provisioned in the authentication provider. Known only to the server and the client (in this case, ZEDEDA). |
| OpenID Connect Endpoint (*) | The endpoint of the authentication provider. Must be OIDC compliant. |
| Scope | OIDC claims to identify application roles. This is useful when application role management is also done at the OIDC provider. By default, the 'roles' claim is used to pick application roles. |
| Default Role for New Users (*) | If no roles are specified via the 'scope' argument, this role is assigned to all new users authenticated by the OIDC provider. |
Third-Party integrations
You can integrate third-party tools, such as Splunk, Rancher, or OpenTelemetry (OTEL) with ZEDEDA Infrastructure Services. The data of all the events generated within your Enterprise is sent to the configured Splunk.
Rancher
- Go to Administration.
- Click on the 'Add Integration' button.
- Add the third-party integration name.
- Select the category from the dropdown list. In this case, it is 'Remote Orchestration.'
- Select from the dropdown list. In this case, it is 'Rancher.'
- Select the authentication type from the dropdown group list: API Token
OpenTelemetry
OTEL metrics export provides a standardized, streaming mechanism to send ZEDEDA platform observability data directly to your preferred monitoring and alerting tools. By integrating edge infrastructure metrics into centralized observability platforms, it allows you to track the health and performance of your edge nodes and applications without relying on inefficient API polling.
Configure the integration
- Go to Enterprise > Third Party Integrations.
- Click the Add Integration card.
- Add the third-party integration name.
- Select the Data integration category from the dropdown list.
- Select the OpenTelemetry(gRPC) integration type from the dropdown list.
- Enter the bearer token in the format of Bearer <your-token>.
- Enter the host in the format of your-otel-collector-hostname (for example, otel-collector.example.com).
- Enter the port in the format of 4317 (the default OTLP/gRPC port, but replace this with your custom port number if applicable).
- (Optional) Toggle Skip Verify to enable TLS certificate verification to be skipped. Use this only in non-production or testing environments where the server uses a self-signed certificate.
- (Optional) Toggle Enable TLS to enable encrypted communication between ZEDEDA and your OpenTelemetry collector endpoint.
- Click Add.
Configure the data stream
- Go to Enterprise > Data Streams.
- Click the Add Data Stream card.
- Select the Device Metrics data streaming type from the dropdown list.
- Add the data stream name.
- Select the Third Party Integration that you previously created.
- (Optional) Toggle Enable Streaming to activate metric streaming to the configured integration immediately.
- Click Add.
Configure the project
- Create or edit a Project.
- Toggle Suppress Streaming Telemetry to disable telemetry streaming for edge nodes in this project, overriding the data stream configuration.