Comments (17)
Hey, why did you stop publishing the portable binary? I need it for docker images
from jaeger-client-cpp.
I love the idea of using https://github.com/tcnksm/ghr. Will get around to it myself when possible unless someone beats me to it.
from jaeger-client-cpp.
Figuring out the dependencies is going to be pretty tedious for jaeger-client-cpp. I was hoping to get a C client out soon enough. That would make linking a lot simpler and the plugin much smaller. Is there an ETA for this feature you had in mind?
from jaeger-client-cpp.
It should take too long. I can provide a PR with a script to build the plugin.
The dependencies should be all linked in and an export map will be used so that they won't clash if the user happens to also be linking to them, so the plugin itself will be completely self-contained. You can see how it works with the zipkin plugin I made: https://github.com/rnburn/zipkin-cpp-opentracing/releases
You can certainly evolve and have other releases produce a different shared library, but I would go forward with what you have.
from jaeger-client-cpp.
OK let me give it a shot now. Thanks for the offer. I'll let you know if I get stuck.
from jaeger-client-cpp.
OK so here's the breakdown. Seeing as I use Hunter, and I turn on -fPIC
using CMake's option here, that means all of my dependencies are built with the same CMake option (Hunter guarantees that except for maybe OpenSSL, which uses autotools). In that case, do I need to bother building opentracing-cpp like you do in the Zipkin example?
About the version map, could I possibly use something less compiler specific like https://cmake.org/cmake/help/v3.1/module/GenerateExportHeader.html?
Which brings me to the next question, how portable is this plugin supposed to be? It seems to only target x86-64 (granted that is pretty much ubiquitous).
from jaeger-client-cpp.
You already have PIC turned on for even your static libraries (https://github.com/jaegertracing/jaeger-client-cpp/blob/master/cmake/toolchain.cmake#L4), so you shouldn't need to do anything with that.
There are some other ways of producing the same effects as an export map (e.g. default everything to have hidden visibility and explicitly mark the functions you want to export); but I think an export map is the least intrusive way to get started.
I'm only targeting linux-amd64 initially. But I mark the architecture in the release binary, so you could certainly add and mark plugins for other platforms if there's demand for them. The expectation is the plugins would be managed the same way as the binary releases in other projects. (See for example a protobuf release where there's attachments for each platform https://github.com/google/protobuf/releases/tag/v3.5.1)
from jaeger-client-cpp.
OK great just making sure. I don't mind the map seeing the single usage here as opposed to changing the code, especially the opentracing-cpp global symbol. In terms of the release strategy, that makes the most sense. Most people are deploying to Linux amd64 as it is.
from jaeger-client-cpp.
BTW - the code in https://github.com/rnburn/cpp-client/tree/plugin/plugin has a script that will build a plugin into /tmp/jaeger-docker-build or wherever you set JAEGER_DOCKER_BUILD_DIR. I wrote it before I knew you were going to work on it. Feel free to copy any part of it if you like.
I also have https://github.com/rnburn/ot-chat-example/tree/master/jaeger which has a docker-compose example with the plugin that I've been testing with.
from jaeger-client-cpp.
@isaachier - I don't think this is quite done yet. Could you attach the shared library built to Jaeger's release?
from jaeger-client-cpp.
@rnburn I don't have a release with this yet but ran locally and produced this from current master (359979c). Had to append .txt
so GitHub would allow upload here.
libjaegertracing_plugin.so.txt
from jaeger-client-cpp.
Could you attach as an asset to Release 0.3.0 like it's done here? I think that's where people would expect to find it.
from jaeger-client-cpp.
@isaachier cf. jaegertracing/jaeger#766
from jaeger-client-cpp.
Even if the automated build isn't done yet, could you attach to the release manually? It would let me go forward with putting in the documentation to envoy.
from jaeger-client-cpp.
I would rather add a new release than attempt backporting the changes on top of an older one.
from jaeger-client-cpp.
But ya let me start on the release now to unblock you.
from jaeger-client-cpp.
See release 0.4.0.
from jaeger-client-cpp.
Related Issues (20)
- Provide access to context HTTP Header name
- Jaeger 32 bit C/C++ client required
- QUESTION: Can not use with hunter manager
- how to release version to real scene
- Unit test: Socket.testFailBind fails when run as "root" HOT 6
- Can we please ditch hunter HOT 1
- Enable ppc64le arch for jaeger-client-cpp
- Unable to build windows in a pipeline.
- Add support for adding tracer tags via config yaml HOT 1
- My jaeger version is 1.23, and the jaeger-collector component has enabled --sampling.strategies-reload-interval, but the collected logs show that the sampling strategy is still old HOT 4
- Envoy - failed to load dynamic library opentracing versions are incomptable
- `RemoteReporter::report()` is blocked
- Default queue size & buffer flush interval are not used when reading configuration from YAML
- Issue facing while trying to build jaeger-client-cpp
- Compilation issue on Ubuntu 20.04 HOT 2
- When the sampling type is rate, the number of actual results is equal to the number of threads multiplied by the configured rate parameter
- warning const' was hidden [-Woverloaded-virtual] when using jaeger client with opentracing libraries
- Enablement TravisCI integration for IBM ppc64le architecture HOT 1
- Deprecate Jaeger C++ SDK HOT 3
- [Bug]: W3C Propagation is wrongfully encoding debug span flag into traceparent HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jaeger-client-cpp.