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

Revise internal cardinality metrics #241

Merged
merged 2 commits into from
Jan 17, 2024
Merged

Revise internal cardinality metrics #241

merged 2 commits into from
Jan 17, 2024

Conversation

brawndou
Copy link
Collaborator

@brawndou brawndou commented Dec 21, 2023

This revises what and how cardinality metrics are reported.

Changes:

  • Cardinality data is emitted by default, as Gauge
  • Names are now prefixed tally.internal. to be consistent with others
  • Added scope cardinality data
  • Cardinality metrics' tags are now consistent with reporter internal metrics

Copy link

codecov bot commented Dec 22, 2023

Codecov Report

Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (8686c7d) 47.85% compared to head (0aa4f89) 47.95%.

❗ Current head 0aa4f89 differs from pull request most recent head 4d9d964. Consider uploading reports for the commit 4d9d964 to get more accurate results

Files Patch % Lines
m3/example/m3_main.go 0.00% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #241      +/-   ##
==========================================
+ Coverage   47.85%   47.95%   +0.09%     
==========================================
  Files          64       64              
  Lines        5993     6006      +13     
==========================================
+ Hits         2868     2880      +12     
- Misses       2685     2686       +1     
  Partials      440      440              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

m3/reporter_integration_test.go Outdated Show resolved Hide resolved
scope_registry.go Outdated Show resolved Hide resolved
scope_registry.go Show resolved Hide resolved
scope_registry.go Outdated Show resolved Hide resolved
counterCardinalityName = "tally.internal.counter_cardinality"
gaugeCardinalityName = "tally.internal.gauge_cardinality"
histogramCardinalityName = "tally.internal.histogram_cardinality"
scopeCardinalityName = "tally.internal.scope_cardinality"
Copy link
Collaborator

Choose a reason for hiding this comment

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

num-active-scopes would be a better name for this.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

done

scope.go Outdated Show resolved Hide resolved
@brawndou brawndou merged commit 2498a0d into uber-go:master Jan 17, 2024
5 checks passed
brawndou added a commit to brawndou/tally that referenced this pull request Jan 23, 2024
* update internal metrics impl

* change scope counter name
brawndou added a commit to brawndou/tally that referenced this pull request Jan 26, 2024
* update internal metrics impl

* change scope counter name
brawndou added a commit to brawndou/tally that referenced this pull request Jan 26, 2024
* update internal metrics impl

* change scope counter name
@brawndou brawndou mentioned this pull request Jan 26, 2024
brawndou added a commit that referenced this pull request Jan 26, 2024
* Revise internal cardinality metrics (#241)

* Backport #221 and #222 to master branch (#243)

* [bug] Ensure that parent scopes do not return closed subscopes (#221)

* TestScope: don't prune from registry when closed (#222)

---------

Co-authored-by: Matt Way <mway@users.noreply.github.com>

---------

Co-authored-by: Matt Way <mway@users.noreply.github.com>
@ptxmac
Copy link

ptxmac commented Mar 13, 2024

This reintroduced #198

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.

3 participants