Skip to content

[OBSDOCS-2678] Clarify prerequisites Quick start with OpenTelemetry #101389

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: standalone-logging-docs-main
Choose a base branch
from
Open

[OBSDOCS-2678] Clarify prerequisites Quick start with OpenTelemetry #101389

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 8 additions & 11 deletions modules/quickstart-opentelemetry.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,11 +8,13 @@ include::snippets/technology-preview.adoc[]
To configure OTLP ingestion and enable the OpenTelemetry data model, follow these steps:

.Prerequisites
* Cluster administrator permissions
* You have access to an {ocp-product-title} cluster with `cluster-admin` permissions.
* You installed the {oc-first}.
* You have access to a supported object store. For example, AWS S3, Google Cloud Storage, {azure-short}, Swift, Minio, or {rh-storage}.

.Procedure

. Install the {clo}, {loki-op}, and {coo-first} from OperatorHub.
. Install the `{clo}`, `{loki-op}`, and `{coo-first}` from OperatorHub.

. Create a `LokiStack` custom resource (CR) in the `openshift-logging` namespace:
Copy link

@anpingli anpingli Oct 30, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we see "here is an example using AWS s3 object store"?

Copy link

@anpingli anpingli Oct 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the storage.schemas.verison must be v13.

+
Expand Down Expand Up @@ -54,7 +56,7 @@ $ oc create sa collector -n openshift-logging
+
[source,terminal]
----
$ oc adm policy add-cluster-role-to-user logging-collector-logs-writer -z collector
$ oc adm policy add-cluster-role-to-user logging-collector-logs-writer -z collector -n openshift-logging
----
+
[NOTE]
Expand All @@ -66,22 +68,17 @@ The `ClusterRole` resource is created automatically during the Cluster Logging O
+
[source,terminal]
----
$ oc project openshift-logging
$ oc adm policy add-cluster-role-to-user collect-application-logs -z collector -n openshift-logging
----
+
[source,terminal]
----
$ oc adm policy add-cluster-role-to-user collect-application-logs -z collector
$ oc adm policy add-cluster-role-to-user collect-audit-logs -z collector -n openshift-logging
----
+
[source,terminal]
----
$ oc adm policy add-cluster-role-to-user collect-audit-logs -z collector
----
+
[source,terminal]
----
$ oc adm policy add-cluster-role-to-user collect-infrastructure-logs -z collector
$ oc adm policy add-cluster-role-to-user collect-infrastructure-logs -z collector -n openshift-logging
----
+
Copy link

@anpingli anpingli Oct 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about move (Create a UIPlugin CR to enable the Log section in the Observe tab) after line 45.
The UIPlugin display logs from lokistack, it doesn't care about if ClusterLogForwarder is running or not.

[NOTE]
Expand Down