PEC-REP/Current/GIMPEGuide/Observability - Revision history

WikiSysop at 10:46, September 29, 2022

2022-09-29T10:46:11Z

Jdruker: Published

2022-02-15T16:49:45Z

Published

Jose.druker@genesys.com: Published

2021-12-16T18:12:36Z

Published

New page

{{ArticlePEServiceObservability
|EnableMonitoring=The Genesys Info Mart services use PodMonitor custom resource definitions (CRDs), which are defined in the Helm charts by default. No additional service-level configuration is required to enable monitoring. See {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=Operations|topic=General_instructions_on_monitoring_solution_for_services}} for information about enabling monitoring for your private edition solution.
|ConfigureMetrics=The metrics that are exposed by the Genesys Info Mart services are available by default. No further configuration is required in order to define or expose these metrics. You cannot define your own custom metrics.

The Metrics pages linked to [[{{FULLPAGENAME}}#MetricsLinks|above]] show some of the metrics the Genesys Info Mart services expose. You can also query Prometheus directly or via a dashboard to see all the metrics available from the Genesys Info Mart services.
|AlertsDefined=Yes
|ExtConfigAlertsBoilerplate=Yes
|Logging=Genesys Info Mart outputs logs to standard output (stdout). GCA and GSP use a structured logging approach, while GIM currently uses an unstructured one.

You can set the log levels for the Genesys Info Mart services in the respective values.yaml files. By default, the GSP and GIM logs are at the INFO level, while GCA logs are at DEBUG level.


}}

@@ Line 1: / Line 1: @@
 {{ArticlePEServiceObservability
-|EnableMonitoring=The Genesys Info Mart services use PodMonitor custom resource definitions (CRDs), which are defined in the Helm charts by default. No additional service-level configuration is required to enable monitoring. See {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=Operations|topic=General_instructions_on_monitoring_solution_for_services}} for information about enabling monitoring for your private edition solution.
+|EnableMonitoring=The Genesys Info Mart services use PodMonitor custom resource definitions (CRDs), which are defined in the Helm charts by default. No additional service-level configuration is required to enable monitoring. See {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=Operations|topic=Monitoring_Approach|anchor=enablemonitoring|display text=Enabling monitoring}} for information about enabling monitoring for your private edition solution.
 |ConfigureMetrics=The metrics that are exposed by the Genesys Info Mart services are available by default. No further configuration is required in order to define or expose these metrics. You cannot define your own custom metrics.

@@ Line 6: / Line 6: @@
 |AlertsDefined=Yes
 |ExtConfigAlertsBoilerplate=Yes
-|Logging=Genesys Info Mart outputs logs to standard output (stdout). GCA and GSP use a structured logging approach, while GIM currently uses an unstructured one.
+|Logging=Genesys Info Mart uses a structured logging approach and outputs logs to standard output (stdout).
 You can set the log levels for the Genesys Info Mart services in the respective values.yaml files. By default, the GSP and GIM logs are at the INFO level, while GCA logs are at DEBUG level.
-<!--See {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=Operations|topic=Logging_approaches|display text=Logging overview and approaches}} and related links in the ''Operations'' guide for more information about logging in private edition, including deployment information and how you can use log collectors (such as Elasticsearch) to extract the logs and viewing tools (such as Kibana) to visualize the data.-->
+See {{Link-AnywhereElse|product=PrivateEdition|version=Current|manual=Operations|topic=Logging_approaches|display text=Logging overview and approaches}} and related links in the ''Operations'' guide for more information about logging in private edition, including deployment information and how you can use log collectors (such as Elasticsearch) to extract the logs and viewing tools (such as Kibana) to visualize the data.
 }}