Uploaded image for project: 'Observability Documentation'
  1. Observability Documentation
  2. OBSDOCS-460

Elasticsearch and fluentd continues being as default even when deprecated long time ago

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • Logging 5.8
    • Logging 5.5, Logging 5.6, Logging 5.7
    • Logging
    • OBSDOCS (Oct 2 - Oct 23) #243, OBSDOCS (Oct 23 - Nov 13) #244, OBSDOCS (Nov 13 - Dev 4) #245

      URL:

      https://docs.openshift.com/container-platform/4.12/logging/cluster-logging.html

      https://docs.openshift.com/container-platform/4.12/logging/cluster-logging-deploying.html

      https://docs.openshift.com/container-platform/4.12/logging/config/cluster-logging-configuring-cr.html

      https://docs.openshift.com/container-platform/4.12/logging/cluster-logging-upgrading.html

      https://docs.openshift.com/container-platform/4.12/logging/cluster-logging-dashboards.html

      https://docs.openshift.com/container-platform/4.12/logging/cluster-logging-uninstall.html

      ISSUE

      Long time ago, Elasticsearch and fluentd were deprecated and it was announced the GA availability of Loki and Vector. 

      All the Logging documentation when you go to installing Logging, or Uninstalling or Configuring is done for Elasticsearch and Fluentd when it should be visible as first reference Vector and Loki and as deprecated and second reference should be Elasticsearch and Fluentd.

       

      EXPECTED

      Able to see all the logging documentation for the current GA: Loki and Vector and as secondary and marked as deprecated Fluentd and Elasticsearch.

      It's not easy to promote the deprecation of Fluentd/Elasticsearch when the default documentation is for them and not for Vector and Loki.

       

       

        There are no Sub-Tasks for this issue.

            abrennan@redhat.com Ashleigh Brennan
            rhn-support-ocasalsa Oscar Casal Sanchez
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: