An Org serves as a tightly isolated bounded context that encompasses all the resources managed by Control Plane. These resources comprise domains, images, workloads, GVCs, users, groups, service accounts, and more.
It's possible for a physical organization, to create multiple 'orgs,' although this is not mandatory. Creating multiple orgs can be beneficial in order to establish complete isolation between environments, for instance.
Refer to the Create an Org guide.
A user can be a member of one or more Orgs.
>
to the right of the current org.Yes
.Control Plane offers the ability to ship all Org logs to an external provider.
Please click here for additional details and configuration instructions.
OpenTelemetry traces are supported and can be configured with the native Control Plane
tracing provider or sent to an OpenTelemetry collector endpoint by using the OpenTelemetry
tracing provider.
The Control Plane tracing provider is the default method for collecting OpenTelemetry traces. They will be accessible for exploration using Grafana by accessing "Metrics" in the sidebar menu of the Console.
The Control Plane tracing provider is the default method for collecting OpenTelemetry traces. They will be accessible for exploration using Grafana by accessing Metrics
in the sidebar menu of the Console.
To enable traces using the Console, navigate to your GVC, click on Tracing
, and choose Control Plane
as the metric provider. Then, configure the sampling percentage and, optionally, the Custom Tags.
Here is an example of a GVC with enabled tracing:
copykind: gvcname: online-boutiquespec:staticPlacement:locationLinks:- //location/aws-eu-central-1- //location/azure-eastus2- //location/gcp-us-west1tracing:provider:controlPlane: {}customTags: {}sampling: 100
Similarly, traces can be sent to an OTEL collector endpoint using the OpenTelemetry
tracing provider.
For details, see the Online Boutique example.
The retention period for logs, metrics and traces defaults to 30 days and can be adjusted for each independently.
Charges apply for storage beyond the 30 day default.
The console UI will automatically sign out if inactive for 15 minutes. This timeout duration is the default setting (for PCI compliance) and can be modified.
This timeout setting (in seconds) can be adjusted from the Info
page when clicking on the Org
link from the left menu.
The permissions below are used to define policies together with one or more of the four principal types:
Permission | Description | Implies |
---|---|---|
edit | Modify org | view |
exec | Grantees can execute all commands on the org | exec.echo |
exec.echo | Grantees can execute the echo command | |
grafanaAdmin | Grantees are made Admin in Grafana, otherwise the role 'Viewer' is assigned | |
manage | Full access | edit, exec, exec.echo, grafanaAdmin, manage, readLogs, readMetrics, readUsage, view, viewAccessReport |
readLogs | Grantees can read logs from all workloads | view |
readMetrics | Grantees can access usage and performance metrics | |
readUsage | Grantees can access usage and billing metrics | |
view | Read-only view: every org member can view their org | |
viewAccessReport | Grantees can inspect the granted access report on all resources within the org |
Displays the permissions granted to principals for the Org.
To view the CLI documentation for an Org, click here.
To view the schema documentation for orgs, click here.