Difference between revisions of "TLM/Current/TLMPEGuide/Planning"
From Genesys Documentation
m (Text replacement - "Genesys Engage [cC]loud" to "Genesys Multicloud CX") |
(Published) |
||
| Line 2: | Line 2: | ||
|DisplayName=Before you begin | |DisplayName=Before you begin | ||
|Context=Find out what to do before deploying Telemetry Service. | |Context=Find out what to do before deploying Telemetry Service. | ||
| + | |ServiceId=97884a5d-324e-4067-8444-8369ca96ffb8 | ||
| + | |IncludedServiceId=17df197d-45b4-4d49-b269-f44d5bdfe5a1 | ||
|LimitationsStatus=Yes | |LimitationsStatus=Yes | ||
|LimitationsText=NA | |LimitationsText=NA | ||
|HelmStatus=No | |HelmStatus=No | ||
| − | |HelmText= | + | |HelmText=Telemetry Service is composed of: |
| − | |||
| − | Telemetry Service is composed of: | ||
*1 Docker Container: '''tlm/telemetry-service:version''' | *1 Docker Container: '''tlm/telemetry-service:version''' | ||
*1 Helm Chart: '''telemetry-service_version.tgz''' | *1 Helm Chart: '''telemetry-service_version.tgz''' | ||
| − | |ThirdPartyStatus= | + | |
| + | For additional information about overriding Helm chart values, see {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|topic=HelmOverrides|display text=Overriding Helm Chart values}} in the ''{{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=PEGuide|display text=Genesys Multicloud CX Private Edition Guide}}''. | ||
| + | |||
| + | For information about downloading Helm charts from JFrog Edge, see {{SuiteLevelLink|helmchart}} in the ''Setting up Genesys Multicloud CX Private Edition'' guide. | ||
| + | |ThirdPartyStatus=Yes | ||
|ThirdPartyText=NA | |ThirdPartyText=NA | ||
|StorageStatus=Yes | |StorageStatus=Yes | ||
| Line 22: | Line 26: | ||
|DependenciesText=For any kind of Telemetry deployment, the following service must be deployed and running before deploying the Telemetry service: | |DependenciesText=For any kind of Telemetry deployment, the following service must be deployed and running before deploying the Telemetry service: | ||
| − | *Genesys Authentication Service | + | *{{Link-AnywhereElse|product=AUTH|version=Current|manual=AuthPEGuide|display text=Genesys Authentication Service}} |
| + | |||
| + | For a look at the high-level deployment order, see {{SuiteLevelLink|deployorder}}. | ||
|GDPRStatus=Yes | |GDPRStatus=Yes | ||
|PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167 | |PEPageType=bf21dc7c-597d-4bbe-8df2-a2a64bd3f167 | ||
}} | }} | ||
Latest revision as of 17:20, December 22, 2021
This topic is part of the manual Telemetry Service Private Edition Guide for version Current of Telemetry Service.
Find out what to do before deploying Telemetry Service.
Related documentation:
RSS:
Download the Helm charts
Telemetry Service is composed of:
- 1 Docker Container: tlm/telemetry-service:version
- 1 Helm Chart: telemetry-service_version.tgz
For additional information about overriding Helm chart values, see Overriding Helm Chart values in the Genesys Multicloud CX Private Edition Guide.
For information about downloading Helm charts from JFrog Edge, see Downloading your Genesys Multicloud CX containers in the Setting up Genesys Multicloud CX Private Edition guide.
Genesys dependencies
For any kind of Telemetry deployment, the following service must be deployed and running before deploying the Telemetry service:
For a look at the high-level deployment order, see Order of services deployment.
Comments or questions about this documentation? Contact us for support!