-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Remove support for OTEL spanmetrics processor #5539
Remove support for OTEL spanmetrics processor #5539
Conversation
Signed-off-by: Vamshi Maskuri <[email protected]>
Signed-off-by: Vamshi Maskuri <[email protected]>
…eger into cleanup-processor
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5539 +/- ##
==========================================
- Coverage 96.20% 96.20% -0.01%
==========================================
Files 327 327
Lines 16021 16006 -15
==========================================
- Hits 15413 15398 -15
Misses 432 432
Partials 176 176
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@yurishkuro Still there any to remove? These are files mainly updated in the PR linked in the ticket for dual support of the processor and connector. And for README, can we keep the migration guide or remove it? |
Signed-off-by: Vamshi Maskuri <[email protected]>
Signed-off-by: Vamshi Maskuri <[email protected]>
@albertteoh PTAL. I have also removed the migration guide. Would you also like me to update the configuration of the spanmetrics connector replacing the migration guide there? |
Signed-off-by: Vamshi Maskuri <[email protected]>
Signed-off-by: Vamshi Maskuri <[email protected]>
Signed-off-by: Vamshi Maskuri <[email protected]>
Signed-off-by: Vamshi Maskuri <[email protected]>
Signed-off-by: Vamshi Maskuri <[email protected]>
Signed-off-by: Vamshi Maskuri <[email protected]>
Looks like the tests need updating. |
Signed-off-by: Vamshi Maskuri <[email protected]>
Yeah! Just fixed now |
@albertteoh The tests are failing as I update with the operation label as expected and converse it failing again with no need for an operation label :) Before:
and this one after updating tests as fails in above unit tests fail:
The current definitions of the functions Any suggestions on it @albertteoh @yurishkuro ? |
Signed-off-by: Vamshi Maskuri <[email protected]>
Signed-off-by: Vamshi Maskuri <[email protected]>
@albertteoh It's 100% hit of test coverage now for this patch :) |
@yurishkuro PTAL and review the changes |
Signed-off-by: Vamshi Maskuri <[email protected]>
@albertteoh @yurishkuro have added back the var operation => span_name. It fails tests and creates confusion about the already existing span_name variable there. Isn't it
|
Signed-off-by: Vamshi Maskuri <[email protected]>
@varshith257 From: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/translator/prometheus/README.md#labels You'll see that one of the normalization steps performed to convert an OTLP attribute name to Prometheus is to: "Drop unsupported characters and replace with underscores (_)" The example given there is to replace |
The two lines mentioned for changing in fn of mock Prometheus Server have updated to span_name. After debugging the metricLabel in reader.go is still pointing to operation in tests though we already changed in reader go. But, I can't pinpoint where still this operation label is emitting from, though we have removed most of it references
I have updated the mapping function for it in assert labels to map operation => span_name |
…leanup-processor
Signed-off-by: Vamshi Maskuri <[email protected]>
Signed-off-by: Vamshi Maskuri <[email protected]>
Signed-off-by: Vamshi Maskuri <[email protected]>
Signed-off-by: Vamshi Maskuri <[email protected]>
@albertteoh PTAL |
## Which problem is this PR solving? - Resolves #5672 - Due to oversight, a bug was introduced in #5539 which changed the attribute name expected by the UI from `operation` to `span_name` ## Description of the changes - Revert those changes ## How was this change tested? `(cd docker-compose/monitor/ && make build dev)` <img width="1910" alt="image" src="https://github.com/jaegertracing/jaeger/assets/3523016/79400073-75f1-4db5-8bef-9a4c439d2852"> ## Checklist - [ ] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [ ] I have signed all commits - [ ] I have added unit tests for the new functionality - [ ] I have run lint and test steps successfully - for `jaeger`: `make lint test` - for `jaeger-ui`: `yarn lint` and `yarn test` Signed-off-by: Yuri Shkuro <[email protected]>
reverted changes to "operation" label #5673 |
## Which problem is this PR solving? - Resolves #5672 - Due to oversight, a bug was introduced in #5539 which changed the attribute name expected by the UI from `operation` to `span_name` ## Description of the changes - Revert those changes ## How was this change tested? `(cd docker-compose/monitor/ && make build dev)` <img width="1910" alt="image" src="https://github.com/jaegertracing/jaeger/assets/3523016/79400073-75f1-4db5-8bef-9a4c439d2852"> ## Checklist - [ ] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [ ] I have signed all commits - [ ] I have added unit tests for the new functionality - [ ] I have run lint and test steps successfully - for `jaeger`: `make lint test` - for `jaeger-ui`: `yarn lint` and `yarn test` Signed-off-by: Yuri Shkuro <[email protected]>
Which problem is this PR solving?
Description of the changes
How was this change tested?
Checklist
jaeger
:make lint test
jaeger-ui
:yarn lint
andyarn test