14 lines
838 B
Markdown
14 lines
838 B
Markdown
# Investigate and design JSON log input handling
|
|
|
|
Figure out what should and can happen if the logs are JSON input. What happens if the JSON is invalid during ingestion. What useful functionality can we have.
|
|
|
|
## Notes
|
|
This is an investigation/design ticket before implementation. Needs a decision on:
|
|
- How JSON-formatted log lines are detected and parsed.
|
|
- What happens on invalid/malformed JSON during ingestion (drop, store raw, flag, error metric, etc).
|
|
- What functionality JSON structure could unlock (field extraction, filtering/querying by field, structured display in the log viewer, etc).
|
|
|
|
## Acceptance criteria
|
|
- A short design decision is written (e.g. via `repowise decision add`) covering: detection, invalid-JSON handling, and prioritized feature ideas.
|
|
- Follow-up implementation ticket(s) filed based on the decision.
|