Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-3075

[release-5.5 ]Remove write_index field from record sent to ES

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • OBSDA-108 - Distribute an alternate Vector Log Collector
    • VERIFIED
    • Hide
      Before this update, log records sent to elasticsearch had an extra field named `write-index` which contains the name of the index to which the logs need to be sent. This field is not a part of the data model.

      After this update, this field is no longer sent.

      Format: Before this update, <X problem> caused <Y situation> (OPTIONAL: under the following <Z conditions>). With this update, <fix> resolves the issue (OPTIONAL: and <agent> can <perform operation> successfully).
      Show
      Before this update, log records sent to elasticsearch had an extra field named `write-index` which contains the name of the index to which the logs need to be sent. This field is not a part of the data model. After this update, this field is no longer sent. Format: Before this update, <X problem> caused <Y situation> (OPTIONAL: under the following <Z conditions>). With this update, <fix> resolves the issue (OPTIONAL: and <agent> can <perform operation> successfully).

      Vector elasticsearch sink can use a record field value to be used as the elasticsearch index. Config generator generates a transform block which determines the index name, and sets it as the value of write_index field. As a side effect, this field is getting sent to elasticsearch as part of the log record.

       

      Use vector config to exclude this field

       

              vimalkum@redhat.com Vimal Kumar
              vimalkum@redhat.com Vimal Kumar
              Ishwar Kanse Ishwar Kanse
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: