Graylog2 / Graylog2/illuminate-documentation

Decide what to do with Target_* Fields

Open
#122 1 comment 0 reactions 0 assignees View on GitHub
needs-discussion triaged
Dominant language
HTML
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Description

What should we do with target_* fields? Should we break these out, or keep them part of user?

Discussion Point

Contributor guide

Open the contributing guide

Research direction

Start by locating the documentation entries for the target_* fields and the user grouping; the issue does not name a file or test. Done means recording and applying a clear decision about whether target_* fields remain part of user or are separated.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.