Just forward w/o transformation possible?

Open
#31 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby

Research direction

No files, tests, or entry points are named. Start by locating the plugin's handling of incoming log records and compare it with the Splunk event JSON shown here; done means deciding whether already-correct payloads can be forwarded without transformation and documenting or implementing that behavior.

Written by the indexing model from the issue text.

Description

The application logging to stdout already writes perfectly correct splunk event json payloads.

{
  "time": 1586785686388,
  "index": "my-index",
  "source": "my-application",
  "event": {
    "severity": "INFO",
    "severity_value": 20000,
    "message": "GET /hello",
    "x-trace-id": "my-id"
  }
}

Is it possible to just pass the data through?

Dominant language
Ruby
Stars
45
Forks
16
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fluent/fluent-plugin-splunk

All issues in fluent/fluent-plugin-splunk

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.