Uploaded image for project: 'Docs for Red Hat Developers'
  1. Docs for Red Hat Developers
  2. RHDEVDOCS-2755

[5.7 prereq] Create Logging API reference docs

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Normal
    • Logging 5.7
    • None
    • Logging
    • devex docs #224 Sep 1-Sep 22, devex docs #225 Sep 22-Oct 13, devex docs #226 Oct 13-Nov 3, devex docs #227 Nov 3-Nov 24, devex docs #228 Nov 24-Dec 15, devex docs #229 Dec 15-Jan 5, devex docs #230 Jan 5-Jan 26, devex docs #231 Jan 26-Feb 16, devex docs #232 Feb 16-Mar 9
    • 8
    • Documentation (Ref Guide, User Guide, etc.)
    • Undefined
    • ---
    • ---

    Attachments

      Issue Links

        blocks

        Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OBSDOCS-176 Assemble multi-line exception stacktrace log messages

        • Critical - To be worked on immediately following BLOCKER issues.
        • Closed

        Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OBSDOCS-219 [CEE.neXT] Adding sections and more clear documentation instructions for LokiStack

        • Critical - To be worked on immediately following BLOCKER issues.
        • Closed

        Task - Represents a small unit of work that is not end-user facing. RHDEVDOCS-4425 Vector LogForwarding to Syslog

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed

        Task - Represents a small unit of work that is not end-user facing. RHDEVDOCS-4430 Loki - Logs-based Alerts

        • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
        • Closed
        is related to

        Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OBSDOCS-136 Logging documentation style improvements

        • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
        • Backlog

        Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OBSDOCS-71 [POC] Observability operators upgrade resource

        • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
        • Backlog

        Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OBSDOCS-149 Resolve issues around forwarding logs to Kafka: MessageSizeTooLarge, compatibility with Kafka versions, docs

        • Undefined - Priority not specified.
        • Backlog

        Bug - A problem that impairs or prevents the functions of the product. RHDEVDOCS-3645 Openshift Logging documentation needs definition of log types.

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed

        Bug - A problem that impairs or prevents the functions of the product. OBSDOCS-150 There is no information about backing up the es and kibana data

        • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
        • Closed

        Bug - A problem that impairs or prevents the functions of the product. RHDEVDOCS-4353 Missing Supported log data output types sections for OpenShift Logging v5.4

        • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
        • Closed

        Bug - A problem that impairs or prevents the functions of the product. OBSDOCS-116 Not including secret in Kafka example Forwarding logs to a Kafka broker

        • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
        • Closed

        Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OBSDOCS-140 Show us how to upgrade Logging using the CLI instead of WebUI

        • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
        • Closed

        Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OBSDOCS-137 To Add the not supported specific on DOC - Forwarding logs to an external Elasticsearch instance

        • Undefined - Priority not specified.
        • Closed

        Task - Represents a small unit of work that is not end-user facing. RHDEVDOCS-2671 Express clearly what's supported and not in the openshift-logging namespace

        • Critical - To be worked on immediately following BLOCKER issues.
        • Closed

        Task - Represents a small unit of work that is not end-user facing. RHDEVDOCS-2988 Update installation: If you're only forwarding log data, installing the internal Elasticsearch log store and Kibana visualization are optional

        • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
        • Closed

        Task - Represents a small unit of work that is not end-user facing. RHDEVDOCS-3280 Create API docs for the ClusterLogForwarder and ClusterLogging APIs

        • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
        • Closed
        links to

        GitHub openshift/openshift-docs#19301: [enterprise-4.3] Edit suggested in file rest_api/index.adoc

        GitHub openshift/openshift-docs#52836: RHDEVDOCS-2755 - API Ref Draft

        GitHub openshift/openshift-docs#56498: RHDEVDOCS-2755 Logging 5.6 API Ref

        GitHub openshift/openshift-docs#56925: [enterprise-4.10] RHDEVDOCS-2755 Logging 5.6 API Ref

        GitHub openshift/openshift-docs#56926: [enterprise-4.11] RHDEVDOCS-2755 Logging 5.6 API Ref

        GitHub openshift/openshift-docs#56927: [enterprise-4.12] RHDEVDOCS-2755 Logging 5.6 API Ref

        GitHub openshift/openshift-docs#56928: [enterprise-4.13] RHDEVDOCS-2755 Logging 5.6 API Ref

        mentioned in

        Page Loading...

        Activity

          People

            landerso@redhat.com Libby Anderson
            rdlugyhe Rolfe Dlugy-Hegwer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: