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

Add metric correctness support to testbed #1713

Merged
merged 2 commits into from
Sep 9, 2020
Merged

Add metric correctness support to testbed #1713

merged 2 commits into from
Sep 9, 2020

Conversation

pmcollins
Copy link
Member

Description: This change adds support for end-to-end metrics correctness tests using generated PICT files.

Link to tracking Issue: #652

Documentation: metrics/doc.go

@codecov
Copy link

codecov bot commented Sep 1, 2020

Codecov Report

Merging #1713 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1713   +/-   ##
=======================================
  Coverage   92.39%   92.39%           
=======================================
  Files         256      256           
  Lines       18190    18190           
=======================================
  Hits        16806    16806           
  Misses        970      970           
  Partials      414      414           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3eb3b66...3c0c8d4. Read the comment docs.

@tigrannajaryan
Copy link
Member

@kbrockhoff can you review please?

@@ -0,0 +1,103 @@
// Copyright The OpenTelemetry Authors
Copy link
Member

Choose a reason for hiding this comment

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

It seems this functionality should be in the testbed package like traces test case. It will need to be used for correctness tests in the contrib project.

Copy link
Member

Choose a reason for hiding this comment

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

Discussed this with @pmcollins, I think we should not "overengineer" things. When we have a real need to use this in contrib, we should understand what is needed to be exported (public) and make the necessary changes. For the moment contrib is not using this.

Copy link
Member

Choose a reason for hiding this comment

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

If that is the approach then this PR is fine. I will change my review status.

@@ -0,0 +1,50 @@
// Copyright The OpenTelemetry Authors
Copy link
Member

Choose a reason for hiding this comment

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

Same as above. Should be in testbed in form that can be used in contrib project.

@@ -0,0 +1,37 @@
// Copyright The OpenTelemetry Authors
Copy link
Member

Choose a reason for hiding this comment

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

This will also be used in contrib project.

@@ -0,0 +1,110 @@
// Copyright The OpenTelemetry Authors
Copy link
Member

Choose a reason for hiding this comment

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

This seems like functionality that should be distributed between existing testbed files. For example, compare function should be part of validator.

@bogdandrutu bogdandrutu merged commit 1405654 into open-telemetry:master Sep 9, 2020
@pmcollins
Copy link
Member Author

Thank you @kbrockhoff for your review. 🙏 Will address your comments in subsequent PRs.

MovieStoreGuy pushed a commit to atlassian-forks/opentelemetry-collector that referenced this pull request Nov 11, 2021
Migrate to using go.opentelemetry.io/proto/otlp
Troels51 pushed a commit to Troels51/opentelemetry-collector that referenced this pull request Jul 5, 2024
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.

4 participants