Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance Tracing with New Metrics, Renames, and Fixes #5991

Merged
merged 6 commits into from
Nov 9, 2024

Conversation

jutaro
Copy link
Contributor

@jutaro jutaro commented Sep 23, 2024

Pull Request Description

Summary

This PR introduces several enhancements and bug fixes to the new tracing system, including two additional metrics, improved naming consistency, and bug fixes to align with the legacy tracing system.
These additions and fixes are introduced to:

  • Enhance traceability by adding essential metrics and harmonizing names across legacy and new systems.
  • Address outstanding bugs to ensure accuracy and reliability in the tracing data.
  • Support workflows dependent on served.block.latest and other core metrics from the legacy system.

New Metrics Added

  1. node.start.time: Captures the node’s start time in POSIX seconds for machine use, providing a standardized timestamp for node initialization.

  2. served.block.latest: A legacy metric previously missing from the new system, now incorporated to track the latest served block and ensure compatibility with established monitoring workflows.

Changes and Fixes

  • Harmonized Metric Names: Standardized metric naming conventions to align with legacy tracing, ensuring consistency across the system and simplifying transition efforts.
  • Bug Fixes: Corrected several issues in the current metrics implementation:
    • Documentation for Churn Action duration metrics.
    • Fixes for metrics associated with forks, client operations, fetches, forging, and CDF counters.
    • Renamed P2P metrics for better alignment with naming conventions.
  • Client Tracer Rewrite: Significant improvements in client tracer functionality to improve accuracy and consistency.

@jutaro jutaro requested a review from a team as a code owner September 23, 2024 08:27
@jutaro jutaro requested a review from mgmeier September 23, 2024 08:27
@mgmeier mgmeier marked this pull request as draft September 26, 2024 18:26
@jutaro jutaro force-pushed the jutaro/metrics_fixes branch 2 times, most recently from 2b001c1 to c84c8fc Compare October 24, 2024 13:14
@jutaro jutaro force-pushed the jutaro/metrics_fixes branch 2 times, most recently from 1fc970f to 98e1751 Compare November 4, 2024 09:01
@jutaro jutaro marked this pull request as ready for review November 4, 2024 09:10
@jutaro jutaro changed the title Add New Metrics to Tracing Enhance Tracing with New Metrics, Renames, and Fixes Nov 4, 2024
rename P2P metrics
Forge metrics and CDFCounters
fetch metrics
fix for client metrics
With forks metrics
Churn Action duration metrics doc
Copy link
Contributor

@mgmeier mgmeier left a comment

Choose a reason for hiding this comment

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

LGTM, thank you @jutaro

@mgmeier mgmeier added this pull request to the merge queue Nov 8, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Nov 8, 2024
@mgmeier mgmeier added this pull request to the merge queue Nov 9, 2024
Merged via the queue into master with commit 85e3898 Nov 9, 2024
25 checks passed
@mgmeier mgmeier deleted the jutaro/metrics_fixes branch November 9, 2024 22:02
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