Skip to content

refactor(telemetry): move client reports into the processor - #1447

Open
giortzisg wants to merge 1 commit into
ref/transport-envelope-contractfrom
ref/telemetry-scheduler
Open

giortzisg wants to merge 1 commit into
ref/transport-envelope-contractfrom
ref/telemetry-scheduler

Conversation

@giortzisg

@giortzisg giortzisg commented Oct 5, 2026 •

Copy link
Copy Markdown
Collaborator

Description

Make the telemetry processor responsible for client reports.

#skip-changelog

Issues

Changelog Entry Instructions

To add a custom changelog entry, uncomment the section above. Supports:

  • Single entry: just write text
  • Multiple entries: use bullet points
  • Nested bullets: indent 4+ spaces

For more details: custom changelog entries

Reminders

Stack created with GitHub Stacks CLI • Give Feedback 💬

@giortzisg
giortzisg added this pull request to stack #1448 October 5, 2026 14:29
Comment thread internal/telemetry/scheduler.go
Comment thread internal/telemetry/processor.go Outdated
Comment thread internal/telemetry/scheduler.go Outdated
Comment thread internal/telemetry/scheduler.go Outdated
Comment thread internal/telemetry/scheduler.go
@giortzisg
giortzisg force-pushed the ref/telemetry-scheduler branch from f3ca4ef to e35f2da Compare October 7, 2026 11:12
@giortzisg
giortzisg force-pushed the ref/telemetry-scheduler branch from e35f2da to c0eacf2 Compare October 8, 2026 12:42
Comment thread internal/telemetry/scheduler.go
Comment thread internal/telemetry/scheduler.go

@cursor cursor Bot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale Bugbot comment from a previous run.

Comment thread internal/telemetry/scheduler.go
@giortzisg
giortzisg force-pushed the ref/telemetry-scheduler branch from c0eacf2 to 5196587 Compare October 8, 2026 14:28
Comment thread internal/telemetry/scheduler.go

@cursor cursor Bot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale Bugbot comment from a previous run.

Comment thread internal/telemetry/scheduler.go
@giortzisg
giortzisg force-pushed the ref/telemetry-scheduler branch from 5196587 to 4b6b9a1 Compare October 9, 2026 08:36
@giortzisg
giortzisg force-pushed the ref/telemetry-scheduler branch from 4b6b9a1 to 583b2f0 Compare October 12, 2026 12:57
@giortzisg
giortzisg removed this pull request from stack #1448 October 12, 2026 13:04
@giortzisg
giortzisg added this pull request to stack #1452 October 12, 2026 13:04
@giortzisg
giortzisg removed this pull request from stack #1452 October 12, 2026 14:07
@giortzisg
giortzisg added this pull request to stack #1455 October 12, 2026 14:08
@giortzisg
giortzisg removed this pull request from stack #1455 October 12, 2026 14:09
@giortzisg
giortzisg added this pull request to stack #1456 October 12, 2026 14:11
@giortzisg
giortzisg force-pushed the ref/telemetry-scheduler branch from 583b2f0 to 2ff991a Compare October 12, 2026 15:46
@giortzisg
giortzisg force-pushed the ref/telemetry-scheduler branch from 2ff991a to 216ae38 Compare October 12, 2026 15:57
@giortzisg
giortzisg force-pushed the ref/telemetry-scheduler branch from 216ae38 to 597fc66 Compare October 13, 2026 10:18
@giortzisg
giortzisg force-pushed the ref/telemetry-scheduler branch from 597fc66 to b955160 Compare October 13, 2026 15:23
@giortzisg
giortzisg force-pushed the ref/telemetry-scheduler branch from b955160 to 314bf56 Compare October 13, 2026 16:27
@giortzisg
giortzisg force-pushed the ref/telemetry-scheduler branch from 314bf56 to bd5fb8d Compare October 15, 2026 17:44
@giortzisg
giortzisg force-pushed the ref/telemetry-scheduler branch from bd5fb8d to 52f9f5c Compare October 15, 2026 18:04

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 52f9f5c. Configure here.

Comment thread internal/telemetry/scheduler.go
Attach client reports during processor submission and send standalone reports periodically or when flushing. After draining the transport, make at most one final report submission and flush it with the same context.

Share envelope submission and rejection accounting between telemetry and standalone reports. Retain legacy transport reporting and leave scheduler concurrency, buffer policies, and transport queues unchanged. Extend the existing integration and rejection test tables.
@giortzisg
giortzisg force-pushed the ref/telemetry-scheduler branch from 52f9f5c to 36cc567 Compare October 16, 2026 10:59
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