Skip to content

Add New Relic tracing to batch route handler#291

Merged
Vruttant1403 merged 1 commit into
gojek:masterfrom
abhiksantra07:feature/nr-batch-tracing
Jul 20, 2026
Merged

Add New Relic tracing to batch route handler#291
Vruttant1403 merged 1 commit into
gojek:masterfrom
abhiksantra07:feature/nr-batch-tracing

Conversation

@abhiksantra07

Copy link
Copy Markdown
Contributor

Wraps ziggurat.kafka-consumer.consumer-handler/process in nr/with-tracing so batch handlers get a NR transaction on the poll thread, matching stream-route (mapper.clj) instrumentation. Also forwards handler exceptions via report-error so they surface in NR's Errors Inbox with transaction context.

Transaction naming: .batch-handler-fn, category "job"
(consistent with stream routes: .handler-fn).

Emits unconditionally — the NR API is a runtime no-op when no agent is attached, so this is safe for users not using New Relic.

Bumps version to 4.13.0 (minor: adds observable behaviour, no breaking changes).

Wraps ziggurat.kafka-consumer.consumer-handler/process in
nr/with-tracing so batch handlers get a NR transaction on the poll
thread, matching stream-route (mapper.clj) instrumentation. Also
forwards handler exceptions via report-error so they surface in NR's
Errors Inbox with transaction context.

Transaction naming: <topic-entity>.batch-handler-fn, category "job"
(consistent with stream routes: <topic-entity>.handler-fn).

Emits unconditionally — the NR API is a runtime no-op when no agent
is attached, so this is safe for users not using New Relic.

Bumps version to 4.13.0 (minor: adds observable behaviour, no
breaking changes).

Co-Authored-By: Claude Opus 4.7 <[email protected]>
@Vruttant1403
Vruttant1403 merged commit 36684fc into gojek:master Jul 20, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants