OBSDOCS-3110: Document HTTP output format parameter

[johnwilkins]

Summary

Documents the new format parameter for HTTP outputs in ClusterLogForwarder, which allows users to specify the data format for logs sent to HTTP endpoints.

Changes

Modified Module:

• logging-http-forward.adoc: Added format field documentation and example

Format Options

• json (default) - Standard JSON format
• ndjson - Newline-delimited JSON for systems that process logs line by line

Use Case

The ndjson format is required for systems like VictoriaLogs and other log aggregation platforms that expect newline-delimited JSON format instead of standard JSON arrays.

Example

outputs:
  - name: http-receiver
    type: http
    http:
      url: 'https://victorialogs.example.com/insert/jsonline'
      format: ndjson

Testing

• ✅ Vale check passed (0 errors, 0 warnings, 3 suggestions)
• ✅ Field description clear and concise
• ✅ Use case explained

Related

• Engineering ticket: LOG-7892
• Upstream commit: cluster-logging-operator 0ad01ba6f
• JIRA: https://redhat.atlassian.net/browse/OBSDOCS-3110

Signed-off-by: John Wilkins jowilkin@redhat.com

🤖 Generated with Claude Code

[openshift-ci-robot]

@johnwilkins: This pull request references OBSDOCS-3110 which is a valid jira issue.

Details

In response to this:

Summary

Documents the new format parameter for HTTP outputs in ClusterLogForwarder, which allows users to specify the data format for logs sent to HTTP endpoints.

Changes

Modified Module:

• logging-http-forward.adoc: Added format field documentation and example

Format Options

• json (default) - Standard JSON format
• ndjson - Newline-delimited JSON for systems that process logs line by line

Use Case

The ndjson format is required for systems like VictoriaLogs and other log aggregation platforms that expect newline-delimited JSON format instead of standard JSON arrays.

Example

outputs:
 - name: http-receiver
   type: http
   http:
     url: 'https://victorialogs.example.com/insert/jsonline'
     format: ndjson

Testing

• ✅ Vale check passed (0 errors, 0 warnings, 3 suggestions)
• ✅ Field description clear and concise
• ✅ Use case explained

Related

• Engineering ticket: LOG-7892
• Upstream commit: cluster-logging-operator 0ad01ba6f
• JIRA: https://redhat.atlassian.net/browse/OBSDOCS-3110

Signed-off-by: John Wilkins jowilkin@redhat.com

🤖 Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[ocpdocs-previewbot]

🤖 Fri Jul 03 18:55:39 - Prow CI generated the docs preview:

https://114512--ocpdocs-pr.netlify.app/openshift-logging/latest/configuring/configuring-log-forwarding.html

[JoaoBraveCoding]

This is more of a collection docs but /lgtm

[jcantrill]

/lgtm

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci]

@johnwilkins: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.