| commit | d226edfe50156abe0a6fa2cd18c29611ba099bab | [log] [tgz] |
|---|---|---|
| author | Roni Riska <roni.riska@nokia.com> | Fri Nov 29 09:13:16 2019 +0200 |
| committer | Roni Riska <roni.riska@nokia.com> | Tue Dec 03 12:50:05 2019 +0200 |
| tree | ee46ddc2c30d699d4261f579ff768b8e7cd27b7f | |
| parent | 8a185f90677984bd001a82988d680ec4d772fb2f [diff] |
Add release yaml A yaml for releasing the package in the packagecloud. Change-Id: Iefbd48afd3cdd1a7355cdb528759387f319b2d55 Signed-off-by: Roni Riska <roni.riska@nokia.com>
The library includes a function for creating a configured tracer instance. It hides the underlaying tracer implementation from the application.
Create a global tracer
#include <opentracing/tracer.h> #include <tracelibcpp/tracelibcpp.hpp> opentracing::Tracer::InitGlobal(tracelibcpp::createTracer("my-service-name"));
Span context propagation between different software components in RIC is using a TextMap carrier and JSON format serialization. The opentracing C++ Readme gives examples how span context inject and extract with textmap can be done. Serialization to JSON can be done with any JSON library.
The trace library currently supports only Jaeger C++ client tracer implementation. The configuration is done using environment variables:
| environment variable | values | default |
|---|---|---|
| TRACING_ENABLED | 1, true, 0, false | false |
| TRACING_JAEGER_SAMPLER_TYPE | const, propabilistic, ratelimiting | const |
| TRACING_JAEGER_SAMPLER_PARAM | float | 0.001 |
| TRACING_JAEGER_AGENT_ADDR | IP addr + port | 127.0.0.1:6831 |
| TRACING_JAEGER_LOG_LEVEL | all, error, none | none |
Meaning of the configuration variables is described in Jaeger web pages. By default a no-op tracer is created.
cmake gcc/c++ opentracing-cpp version 1.5.0
mkdir build cd build cmake .. make
To run unit tests the project needs to be configured with testing option cmake -DWITH_TESTING=ON .. make check Or with output CTEST_OUTPUT_ON_FAILURE=1 make check
Unit testing generates also coverage data. To get that in html format run commands, assuming you are building in build dir under the tracelibcpp
lcov -c --no-external --base-directory $(dirname $PWD) --directory . --output-file cov.info genhtml cov.info
Binary packages of the libary can be created with make package target, or with the Dockerfile in the ci directory.
The Docker build executes unit tests and compiles binary packages which can then be exported from the container by running it and giving the target directory as a command line argument. The target directory must mounted to the container.
# Build the container docker build -t tracelibcpp -f ci/Dockerfile . # Export binary packages to /tmp docker run -v /tmp:/tmp tracelibcpp /tmp
See LICENSES.txt file.