Difference between revisions of "TLM/Current/TLMPEGuide/Overview"
(Published) |
|||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 2: | Line 2: | ||
|Standalone=No | |Standalone=No | ||
|DisplayName=About Telemetry Service | |DisplayName=About Telemetry Service | ||
| − | |Context=Learn about Telemetry Service and how it works in Genesys | + | |Context=Learn about Telemetry Service and how it works in Genesys Multicloud CX private edition. |
|ComingSoon=No | |ComingSoon=No | ||
|Section={{Section | |Section={{Section | ||
|alignment=Vertical | |alignment=Vertical | ||
| − | |structuredtext=The Telemetry Service is designed to act as an observability gateway to gather telemetry data, metrics, and logs for Genesys Multicloud software that has services running outside the data center and out of range of the Cloud Observability framework like Agent | + | |structuredtext=The Telemetry Service is designed to act as an observability gateway to gather telemetry data, metrics, and logs for Genesys Multicloud software that has services running outside the data center and out of range of the Cloud Observability framework like Agent Workspace, Genesys Softphone, etc. |
Once gathered by the Telemetry Service, those metrics and logs are stored in the same data sources as the standard services running inside the data center. | Once gathered by the Telemetry Service, those metrics and logs are stored in the same data sources as the standard services running inside the data center. | ||
| Line 25: | Line 25: | ||
**Trigger incidents in an Incident Response Platform when values are hitting some thresholds. | **Trigger incidents in an Incident Response Platform when values are hitting some thresholds. | ||
*Accelerate troubleshooting during incidents. | *Accelerate troubleshooting during incidents. | ||
| + | |Status=No | ||
| + | }}{{Section | ||
| + | |sectionHeading=Supported Kubernetes platforms | ||
| + | |anchor=#kubernetes | ||
| + | |alignment=Vertical | ||
| + | |structuredtext=Telemetry Service is supported on the following cloud platforms: | ||
| + | |||
| + | *Azure Kubernetes Service (AKS) | ||
| + | *Google Kubernetes Engine (GKE) | ||
| + | |||
| + | See the {{Link-AnywhereElse|product=ReleaseNotes|version=Current|manual=GenesysEngage-cloud|topic=Telemetry}} for information about when support was introduced. | ||
|Status=No | |Status=No | ||
}} | }} | ||
|PEPageType=f94c5001-0cfd-4352-ace3-a27b07d5f3a1 | |PEPageType=f94c5001-0cfd-4352-ace3-a27b07d5f3a1 | ||
}} | }} | ||
Latest revision as of 08:32, February 28, 2023
Contents
Learn about Telemetry Service and how it works in Genesys Multicloud CX private edition.
The Telemetry Service is designed to act as an observability gateway to gather telemetry data, metrics, and logs for Genesys Multicloud software that has services running outside the data center and out of range of the Cloud Observability framework like Agent Workspace, Genesys Softphone, etc.
Once gathered by the Telemetry Service, those metrics and logs are stored in the same data sources as the standard services running inside the data center.
The microservice supports the following API:
- An endpoint to allow remote apps (e.g., applications running in customer environment) to push their traces for a centralized treatment.
- An endpoint to allow remote apps to push metrics for centralized treatment. Metrics are aggregated by Telemetry service, and available as a Prometheus-compliant data format for building dashboards and alerts.
- An endpoint allowing remote apps to push events for centralized treatment. Events are aggregated by Telemetry service, and available as a Prometheus-compliant data format for building dashboards and alerts.
Remote client-side applications can be browser-based interfaces like WWE, as well as executables running on customer premises like Genesys Softphone.
This Telemetry service serves two main goals:
- Proactive detection of issues:
- Telemetry Service can aggregate information coming from client-side in forms of Metric and Events data.
- It allows monitoring the client-side activity in any monitoring platforms for performance, active functionalities, incidents.
- Trigger incidents in an Incident Response Platform when values are hitting some thresholds.
- Accelerate troubleshooting during incidents.
Supported Kubernetes platforms
Telemetry Service is supported on the following cloud platforms:
- Azure Kubernetes Service (AKS)
- Google Kubernetes Engine (GKE)
See the Telemetry Service Release Notes for information about when support was introduced.