2장. Installing end-to-end observability


중요

The end-to-end observability stack is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope.

The ObservabilityInstaller custom resource definition (CRD) can be used to install the end-to-end observability stack.

2.1. Distributed tracing

The distributed tracing capability installs the OpenTelemetry Collector, Tempo and the distributed tracing UI plugin.

Procedure

  1. Install distributed tracing by using the ObservabilityInstaller resource.

    apiVersion: observability.openshift.io/v1alpha1
    kind: ObservabilityInstaller
    metadata:
      name: tracing
      namespace: observability 
    1
    
    spec:
      capabilities:
        tracing:
          enabled: true  
    2
    
          operators:
            install: true 
    3
    
          storage:
            objectStorage: 
    4
    
    ...
    1
    Namespace where the ObservabilityInstaller CR is created. The namespace should contain the secrets referenced in the object storage configuration.
    2
    Enables the tracing capability. This installs the OpenTelemetry Collector, Tempo and all necessary configuration.
    3
    Installs the operators required by the tracing capability. The default is true.
    4
    Required object storage configuration for the tracing capability. This is used to store traces in an object storage service.
  2. Configure S3 object storage

          storage:
            objectStorage:
              s3:
                bucket: <bucket_name> 
    1
    
                endpoint: <s3_endpoint> 
    2
    
                accessKeyID: <access_key_id> 
    3
    
                accessKeySecret: 
    4
    
                  name: s3-access-secret
                  key: access_key_secret
                region: us-east-1 
    5
    1
    Name of the bucket to store data in.
    2
    Endpoint of the S3-compatible object storage service.
    3
    Access key ID for the S3-compatible object storage service.
    4
    Secret containing the access key secret for the S3-compatible object storage service.
    5
    AWS region for the S3 bucket.

    Use the following command to create the secret containing the access key:

    $ oc create secret generic s3-access-secret \
    --from-literal=access_key_secret="secret"
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 문서 정보

Legal Notice

Theme

© 2026 Red Hat
맨 위로 이동