SUPER_ADMIN
role.http://localhost:3100
.data.token
field is the authentication token we need.admin
is automatically created for the new tenant. The login details are the values in email
and admin.password
.SUPER_ADMIN
users to login to any tenant on an installation.data.id
. We'll make use of the authentication token to get the Replex token:Multitenancy Setup
above on the step 2.labels.<LABEL_NAME>:<LABEL_VALUE>
- represents resource labels, where key is LABEL_NAME
and value is LABEL_VALUE
, e.g. labels.app:replex-server
.namespace:<NAMESPACE_NAME>
- represents resources namespace, e.g. namespace:monitoring
.key:<LABEL_NAME>
- represents label name that must appear in stats, e.g. key:app
.filters
parameter to query stats:filters=labels.labelKey1:labelValue1 OR (labels.labelKey1:labelValue2 AND namespace:nsName1)
labelKey1
and value labelValue1
or resources that are in namespace nsName1
and have labels key labelKey1
with value labelValue2
.filters=labels.labelKey1:labelValue1 AND namespace:nsName1
labelKey1
and value labelValue1
and belong to namespace nsName1
.filters=namespace:nsName1 OR namespace:nsName2
nsName1
or nsName2
.filters=namespace:nsName1 AND key:labelKey1
nsName1
and have label keys such as labelKey1
.production
, development
, test
file:
if specifying a file path.file:
if specifying a file path.enable
, disable
EMAIL_MODE
is enableEMAIL_MODE
is enable