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

[chore] Make package naming more consistent #6289

Merged
merged 4 commits into from
Dec 2, 2024

Conversation

mahadzaryab1
Copy link
Collaborator

@mahadzaryab1 mahadzaryab1 commented Dec 2, 2024

Which problem is this PR solving?

Description of the changes

  • Perform the following package renames
    • plugin/metrics to plugin/metricstore
    • storage/metricsstore to storage/metricstore
    • prometheus/metricsstore to prometheus/metricstore
  • Renames storage.MetricsFactory to storage.MetricStoreFactory

How was this change tested?

  • CI

Checklist

@mahadzaryab1 mahadzaryab1 marked this pull request as ready for review December 2, 2024 01:43
@mahadzaryab1 mahadzaryab1 requested a review from a team as a code owner December 2, 2024 01:43
@dosubot dosubot bot added the area/storage label Dec 2, 2024
Copy link

codecov bot commented Dec 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.20%. Comparing base (88777f5) to head (2adc60a).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #6289   +/-   ##
=======================================
  Coverage   96.20%   96.20%           
=======================================
  Files         356      356           
  Lines       20432    20432           
=======================================
  Hits        19656    19656           
  Misses        587      587           
  Partials      189      189           
Flag Coverage Δ
badger_v1 8.90% <ø> (ø)
badger_v2 1.62% <0.00%> (ø)
cassandra-4.x-v1-manual 14.84% <ø> (ø)
cassandra-4.x-v2-auto 1.56% <0.00%> (ø)
cassandra-4.x-v2-manual 1.56% <0.00%> (ø)
cassandra-5.x-v1-manual 14.84% <ø> (ø)
cassandra-5.x-v2-auto 1.56% <0.00%> (ø)
cassandra-5.x-v2-manual 1.56% <0.00%> (ø)
elasticsearch-6.x-v1 18.60% <ø> (ø)
elasticsearch-7.x-v1 18.68% <ø> (ø)
elasticsearch-8.x-v1 18.84% <ø> (ø)
elasticsearch-8.x-v2 1.61% <0.00%> (-0.01%) ⬇️
grpc_v1 10.37% <ø> (ø)
grpc_v2 7.86% <0.00%> (-0.01%) ⬇️
kafka-v1 8.58% <ø> (ø)
kafka-v2 1.62% <0.00%> (ø)
memory_v2 1.62% <0.00%> (+<0.01%) ⬆️
opensearch-1.x-v1 18.73% <ø> (ø)
opensearch-2.x-v1 18.73% <ø> (ø)
opensearch-2.x-v2 1.61% <0.00%> (-0.01%) ⬇️
tailsampling-processor 0.45% <0.00%> (ø)
unittests 95.11% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

@yurishkuro yurishkuro merged commit d1a8ece into jaegertracing:main Dec 2, 2024
54 checks passed
yurishkuro pushed a commit that referenced this pull request Dec 2, 2024
## Description of the changes
- This is an extension of
#6289 to regenerate the
mocks and remove the existing mock for `storage.MetricStoreFactory`

## How was this change tested?
- CI

## Checklist
- [x] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [x] I have signed all commits
- [x] I have added unit tests for the new functionality
- [x] I have run lint and test steps successfully
  - for `jaeger`: `make lint test`
  - for `jaeger-ui`: `yarn lint` and `yarn test`

---------

Signed-off-by: Mahad Zaryab <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

How to capture storage metrics
2 participants