TLM/Current/TLMPEGuide/Observability - Revision history

WikiSysop at 07:30, July 27, 2022

2022-07-27T07:30:53Z

Xavier: Published

2021-12-22T17:20:16Z

Published

New page

{{ArticlePEServiceObservability
|EnableMonitoring=Telemetry Service does not expose any specific metrics for monitoring. You can use standard Kubernetes metrics, as delivered by cAdvisor, of the kind that apply to any pod of the same nature.
|ConfigureMetrics=No additional service-level configuration is required to enable monitoring for Telemetry Service.
|AlertsDefined=Yes
|ExtConfigAlertsBoilerplate=Yes
|Logging=Telemetry Service sends logs to '''stdout'''.

Telemetry Service logs are structured so that log documents can be split into two distinct indexes: one for the Core Telemetry activity and the other for the Telemetry client logs.
}}

← Older revision		Revision as of 07:30, July 27, 2022
Line 7:		Line 7:

	Telemetry Service logs are structured so that log documents can be split into two distinct indexes: one for the Core Telemetry activity and the other for the Telemetry client logs.		Telemetry Service logs are structured so that log documents can be split into two distinct indexes: one for the Core Telemetry activity and the other for the Telemetry client logs.
		+
		+	The '''traceId''' attribute of the '''Telemetry log Contract''' is available to all Telemetry clients by default. This allows logs sent through Telemetry to meet the pre-condition for distributed tracing Observability goal.
	}}		}}