Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Implement ECS-Compatibility Mode

Open
  • Is something wrong?
#12 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
Domain
backend

Research direction

The issue does not name specific files or tests. Start by locating the msgpack codec's event-decoding entry point and reviewing the project's ECS-compatibility conventions; determine whether decoded fields can conflict with ECS and whether a target namespace is required. Done means either implementing and testing ECS-Compatibility mode or documenting that the codec is already compatible.

Written by the indexing model from the issue text.

Description

As a part of the effort to make plugins able to run in an ECS-Compatible manner by default in an upcoming release of Logstash, this plugin needs to either implement an ECS-Compatibility mode or certify that it does not implicitly use fields that conflict with ECS.

Since this Codec produces events verbatim from the encoded structure of the input it is given, it may benefit from requiring a target => ... namespace to be provided when in ECS-Compatibility mode.

Dominant language
Ruby
Stars
5
Forks
10
No merged PRs in 30d

Getting set up

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 logstash-plugins/logstash-codec-msgpack

All issues in logstash-plugins/logstash-codec-msgpack

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.