GIM metrics and alerts

Find the metrics GIM exposes and the alerts defined for GIM.

Related documentation:

• How Reporting works

Service	CRD or annotations?	Port	Endpoint/Selector	Metrics update interval
GIM	PodMonitor	8249	Endpoint: /metrics Selector: selector: matchLabels: app: {{ template "fullname" . }} where the value of fullname depends on .Values.tenant_id.	30 seconds

Metrics

The following metrics are defined for the GIM service.

Metric and description	Metric details	Indicator of
gim_server_state The state of the GIM server. Valid values are: 0 — starting 1 — running -1 — failing once -2 — failing twice -3 — failing three or more times in a row	Unit: Type: Gauge Label: applicationName gim_version built schema_version Sample value:	Error
gim_failed_jobsteps Number of failed job steps.	Unit: Type: Gauge Label: Sample value:	Error
gim_number_failed_kafkajob Number of times the KAFKA step in the transform job failed.	Unit: Type: Gauge Label: applicationName Sample value:	Error
gim_issues_total Number of encountered issues.	Unit: Type: Counter Label: applicationName issue Sample value:	Error
gim_kafka_timestamp_millis Maximum Kafka timestamp per topic per partition, in milliseconds since the Unix Epoch.	Unit: milliseconds Type: Gauge Label: Sample value:	Latency
gim_kafka_timestamp_behind Kafka latency per topic per partition, in milliseconds. Latency is calculated as (current system time) minus (maximum timestamp received). Therefore, this metric can grow if a topic or partition is idle and no records are received.	Unit: milliseconds Type: Gauge Label: applicationName topic partition Sample value:	Latency

Alerts

No alerts are defined for Genesys Info Mart.