feat(schema): wire proto-generated types into packageLogs.ts
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- backend
Research direction
Start by reading packageLogs.ts, the generated types in log_pb.ts, and the TODO in types.d.ts. Trace how current log objects and buildAttrs() are assembled, then verify that the new output follows the proto field names and nested metadata shape while HttpLegacyJsonExporter still preserves the v2.x format.
Written by the indexing model from the issue text.
Description
Summary
Replace the untyped Logging.Log = JSONObject with proto-generated types (RawLog, IntervalLog, CustomLog) from log_pb.ts in packageLogs.ts.
Breaking Changes
This changes the default JSON output format:
- Fields restructured to match proto schema (nested
metadataobject) - Field renames:
type→eventType,scrnRes→screenResolution buildAttrs()stopsJSON.parse()-ing attribute values (always strings)logTypevalues may change (raw→LOG_TYPE_RAW)
Migration Path
HttpLegacyJsonExporterpreserves v2.x JSON format- Users can opt into legacy format via
exporterType: 'http-json-legacy'
Depends On
- #105 (proto schema — merged)
- #139 (LogExporter interface)
Related
- Resolves the TODO on line 77 of types.d.ts:
// TODO: Switch to protobuf for managing log types
- Dominant language
- Jupyter Notebook
- Stars
- 30
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/flagon
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
process
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Discuss enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
enhancement experimental
Difficulty 5/5 Over a week Newbie friendliness 42/100
-
enhancement Userale
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Similar issues
-
area/sessions comp/cron comp/gateway P2 sweeper:risk-message-delivery sweeper:risk-session-state type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#118863 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
use-agent-os/agent-os#3312 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
needs-acceptance wg/data-plane-networking
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vllm-project/semantic-router#4024 · 1 comment ·