phughk/ottyl
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Create tickets

Browse Source
This commit is contained in:
Hugh Kaznowski
2026-09-05 18:31:22 +01:00
parent 0a21582282
commit 893464b3b1
13 changed files with 112 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tickets/003-json-log-ingestion-support.md
+13
View File
@@ -0,0 +1,13 @@
# 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.