-
Task
-
Resolution: Done
-
Blocker
-
None
-
1
-
False
-
-
False
-
https://github.com/openshift/openshift-docs/pull/93342, https://github.com/openshift/openshift-docs/pull/93360, https://github.com/openshift/openshift-docs/pull/94803, https://github.com/openshift/openshift-docs/pull/94932, https://github.com/openshift/openshift-docs/pull/94933, https://github.com/openshift/openshift-docs/pull/94934, https://github.com/openshift/openshift-docs/pull/94935, https://github.com/openshift/openshift-docs/pull/94936
-
-
Act on Pavol's request in https://github.com/openshift/openshift-docs/pull/93342#discussion_r2088560521
Need clarity on supported lokiStack configurations with OpenTelemetry when Customers use Red Hat Loki.
When Loki is used with openshift-logging supported teants are:
~~~
Valid tenant types are application, audit, and infrastructure.
~~~
[+]https://docs.redhat.com/en/documentation/openshift_container_platform/4.16/html/logging/logging-6-2#logging-loki-retention_log6x-loki-6.2
RH Loki Operator currently allows (Or does not reject) other tenant modes to as per : https://loki-operator.dev/docs/api.md/#loki-grafana-com-v1beta1-ModeType
How every only supported by Loki used with openshift-logging is as above
OTEL team only supports sending data to a supported lokistack instance via the application tenant with no customization wrt to the tenant This should be mentioned in doc
- documents
-
TRACING-5360 Clarifying Supported LokiStack Configurations with OpenTelemetry
-
- Closed
-
- links to