Bug 2068542 - Logging pod names
Summary: Logging pod names
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.9
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
: ---
Assignee: Claire Bremble
QA Contact: Xiaoli Tian
Claire Bremble
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-25 16:03 UTC by Charles Benon
Modified: 2023-03-01 18:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-03-01 18:15:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHDEVDOCS-4463 0 None None None 2022-09-19 15:59:48 UTC

Description Charles Benon 2022-03-25 16:03:34 UTC
Document URL: https://docs.openshift.com/container-platform/4.9/logging/config/cluster-logging-collector.html

Section Number and Name: All outputs mentioning running container

Describe the issue: The output from the documentation is different from the output of a freshly deployed system with default values:



You should see several pods for OpenShift Logging, Elasticsearch, Fluentd, and Kibana similar to the following list:
    cluster-logging-operator-cb795f8dc-xkckc
    elasticsearch-cdm-b3nqzchd-1-5c6797-67kfz
    elasticsearch-cdm-b3nqzchd-2-6657f4-wtprv
    elasticsearch-cdm-b3nqzchd-3-588c65-clg7g
    fluentd-2c7dg
    fluentd-9z7kk
    fluentd-br7r2
    fluentd-fn2sb
    fluentd-pb2f8
    fluentd-zqgqx
    kibana-7fb4fd4cc9-bvt4p

From a running system in 4.9:
oc get pods -n openshift-logging
NAME                                            READY   STATUS      RESTARTS      AGE
cluster-logging-operator-66fb569ff-84rfc        1/1     Running     0             29h
collector-6wmt8                                 2/2     Running     6             7d22h
collector-8g6m5                                 2/2     Running     6             7d22h
collector-bdlh8                                 2/2     Running     8 (29h ago)   7d22h
collector-mjfdr                                 2/2     Running     12            7d22h
collector-scq6s                                 2/2     Running     10            7d22h
collector-tbhk2                                 2/2     Running     2             7d22h
collector-zkdnv                                 2/2     Running     6             7d22h
elasticsearch-cdm-l6mw7xup-1-5dbf7d9dbc-lr25h   2/2     Running     0             28h
elasticsearch-cdm-l6mw7xup-2-67b8c4cdbd-d6mwt   2/2     Running     0             29h
elasticsearch-cdm-l6mw7xup-3-588d7b7fd9-vql4l   2/2     Running     0             28h
elasticsearch-im-app-27470400--1-c6qbx          0/1     Completed   0             2m26s
elasticsearch-im-audit-27470400--1-d4b9l        0/1     Completed   0             2m26s
elasticsearch-im-infra-27470400--1-7xzcr        0/1     Completed   0             2m26s
kibana-85d5f5f99-6cqfl                          2/2     Running     0             29h

Changes:
-fluentd is showing as collector
-elasticsearch-im is also there

Suggestions for improvement: 
I think the documentation should be edited to reflect the right outputs

Additional information:

Comment 2 Kathryn Alexander 2023-03-01 18:15:42 UTC
All open BZs in this project will be migrated to Jira in the near future. Because this BZ has already been cloned into Jira, I am closing it now to reduce the number of duplicate Jiras.

This bug will be triaged for future work on the Jira issue that is shown in the Links section.


Note You need to log in before you can comment on or make changes to this bug.