Apps/ImageApi
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

otel: revert HTTP transport, keep gRPC #78

Merged
cameron merged 1 commits from fix/otlp-revert-to-grpc into master 2026-05-06 22:36:10 +00:00
Conversation 0 Commits 1 Files Changed 3 +31 -5
cameron commented 2026-05-06 22:36:00 +00:00
Owner
Copy Link

The HTTP/protobuf exporter never sent any traffic in prod (tcpdump
on port 4318 showed nothing) despite the receiver path being correct
and the bridge wiring being intact (logs reached journalctl via the
stdout exporter). Likely the BatchLogProcessor + reqwest-client combo
isn't getting the right runtime context, but debugging that on a live
deployment isn't worth holding up the rest of the speedups.

Restoring grpc-tonic transport so prod observability comes back. The
remaining build-time wins on this branch (mold linker, system sqlite3,
profile.dev tweaks, lockfile-only dep refresh) deliver most of the
original savings without touching telemetry. Operator: revert
OTLP_OTLS_ENDPOINT in prod from port 4318 back to 4317.

HTTP transport remains a viable follow-up — needs to be debugged
against a local SigNoz instance with internal SDK error visibility
enabled, on its own branch.

Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com

The HTTP/protobuf exporter never sent any traffic in prod (tcpdump on port 4318 showed nothing) despite the receiver path being correct and the bridge wiring being intact (logs reached journalctl via the stdout exporter). Likely the BatchLogProcessor + reqwest-client combo isn't getting the right runtime context, but debugging that on a live deployment isn't worth holding up the rest of the speedups. Restoring grpc-tonic transport so prod observability comes back. The remaining build-time wins on this branch (mold linker, system sqlite3, profile.dev tweaks, lockfile-only dep refresh) deliver most of the original savings without touching telemetry. Operator: revert OTLP_OTLS_ENDPOINT in prod from port 4318 back to 4317. HTTP transport remains a viable follow-up — needs to be debugged against a local SigNoz instance with internal SDK error visibility enabled, on its own branch. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
cameron added 1 commit 2026-05-06 22:36:01 +00:00
otel: revert HTTP transport, keep gRPC ecd49fd053 
The HTTP/protobuf exporter never sent any traffic in prod (tcpdump
on port 4318 showed nothing) despite the receiver path being correct
and the bridge wiring being intact (logs reached journalctl via the
stdout exporter). Likely the BatchLogProcessor + reqwest-client combo
isn't getting the right runtime context, but debugging that on a live
deployment isn't worth holding up the rest of the speedups.

Restoring grpc-tonic transport so prod observability comes back. The
remaining build-time wins on this branch (mold linker, system sqlite3,
profile.dev tweaks, lockfile-only dep refresh) deliver most of the
original savings without touching telemetry. Operator: revert
OTLP_OTLS_ENDPOINT in prod from port 4318 back to 4317.

HTTP transport remains a viable follow-up — needs to be debugged
against a local SigNoz instance with internal SDK error visibility
enabled, on its own branch.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
cameron merged commit 2acc525e73 into master 2026-05-06 22:36:10 +00:00
cameron deleted branch fix/otlp-revert-to-grpc 2026-05-06 22:36:11 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
cameron
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Apps/ImageApi#78
Delete Branch "fix/otlp-revert-to-grpc"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?