apache / apache/flagon

feat(otel): OTel Collector receiver plugin for Flagon JSON

Open
#144 0 comments 0 reactions 0 assignees View on GitHub
enhancement experimental
Dominant language
Jupyter Notebook
Stars
30
Forks
15
PR merge metrics
No merged PRs in 30d

Description

## Summary

Build a custom OTel Collector receiver (`flagonreceiver`) that accepts Flagon's existing JSON format and converts it to OTLP LogRecords server-side.

## Motivation

For users who can't change the client (e.g., already deployed v2.x UserALE) but want OTel on the backend.

## Design

- Written in Go (Collector plugin requirement)
- Accepts POST JSON on configurable HTTP path
- Maps Flagon JSON fields → OTLP LogRecords
- Registers as a standard Collector component
- Could be contributed to `opentelemetry-collector-contrib`

## Structure

```
collector/flagonreceiver/
factory.go
receiver.go
config.go
README.md
```

## Priority

Lower priority than client-side OTLP exporter (#140). Build when there's user demand.

## Depends On

- #140 (OTLP exporter — proves the attribute mapping works)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading issue #140 to understand the attribute mapping and dependency, then review the proposed collector/flagonreceiver/factory.go, receiver.go, config.go, and README.md structure. Define the receiver's HTTP path, Flagon JSON to OTLP LogRecord behavior, standard component registration, and documentation before implementation; done means the receiver accepts the existing JSON format and produces the expected OTLP records.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend-api-design, observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.