Add support for Opensearch client span - #871
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #871 +/- ##
==========================================
- Coverage 55.15% 55.10% -0.05%
==========================================
Files 251 251
Lines 21481 21494 +13
==========================================
- Hits 11847 11845 -2
- Misses 8818 8832 +14
- Partials 816 817 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
mmat11
left a comment
There was a problem hiding this comment.
left some comments, CI is failing, probably a rebase is needed
1a3338d to
3ae6df6
Compare
mmat11
left a comment
There was a problem hiding this comment.
left a couple more comments, lgtm!
4aee72f to
fb4aaab
Compare
|
Can we add a row for opensearch in devdocs/features.md? |
Oh, sure! |
grcevski
left a comment
There was a problem hiding this comment.
LGTM! Thanks for adding this! I'm good to merge, we can maybe just address Nimrod's last comment about 3.0.0+.
Signed-off-by: Giuseppe Ognibene <giuseppe.ognibene@coralogix.com>
Signed-off-by: Giuseppe Ognibene <giuseppe.ognibene@coralogix.com>
fdfa55d to
64930c1
Compare
Done! :) |
This PR introduces support for Opensearch client span, continuing the work already done for Elasticsearch (#801 and #853)
Opensearch doesn't have an opentelemetry semconv, so I reused Elasticsearch's with the only difference being the
db.system.namefield.Moreoveor, to avoid duplicating code, I rewrote the tests and the python testserver to make it generic.