Skip to content

Auron MetricNode periodic updates #2189

Open

Description

@Tartarus0zm

Auron's current metric design is tailored for batch processing scenarios, where metrics are updated only after a task has completed.
However, in Flink environments, tasks are long-running, so we need to update metrics periodically.
For more details, see rt.rs

Image

Activity

  1. qingfei1994 commented on Aug 18, 2026

    @qingfei1994

    I'd like to work on this issue. Is it still available?

  2. Tartarus0zm commented on Aug 19, 2026

    @Tartarus0zm
    ContributorAuthor

    hi @qingfei1994 assigned to you

  3. Tartarus0zm commented on Aug 31, 2026

    @Tartarus0zm
    ContributorAuthor

    hi @qingfei1994 is anything update for this issue?

  4. added a commit that references this issue on Aug 31, 2026
  5. qingfei1994 commented on Aug 31, 2026

    @qingfei1994

    Yes, will create a draft pull request for this.
    Summary is as below:

    • Periodic native metric publish on a tokio interval, sending positive deltas so incremental MetricNode.add does not double-count.
    • Config auron.metrics.update.interval.ms (default 1000; 0 = finalize-only).
    • FlinkMetricNode.fromPlan so Kafka (including fused Project[Filter[KafkaScan]]) and Calc share a plan-shaped metric tree for getChild(i).
  6. added 3 commits that reference this issue on Aug 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions