-
Ticket
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
False
-
None
-
False
-
-
After enabling the monitor tab, the customer sees the below log messages in the gateway pod.
level=info name=observatorium ts=2024-10-27T17:39:14.940889639Z caller=openshift.go:532 msg="failed to authenticate, no serviceaccount bearer token or mTLS certs provided" level=info name=observatorium ts=2024-10-14T10:33:26.415013939Z caller=openshift.go:436 msg="fallback to read cookie, no serviceaccount bearer token or mTLS certs provided"
There are no issues while accessing the Jaeger UI, and no issues with querying traces and monitoring tabs.
The document followed to enable the monitor tab.
https://docs.redhat.com/en/documentation/openshift_container_platform/4.15/html/distributed_tracing/distributed-tracing-platform-tempo#distr-tracing-tempo-config-spanmetrics_opentelemetry-collector-configuration_distr-tracing-tempo-configuring
The customer confirms that they are receiving those logs when the Jaeger UI is accessed.
