opentelemetry-cpp-contrib
opentelemetry-cpp-contrib copied to clipboard
open-telemetry
[Log4cpp](https://log4cpp.sourceforge.net/#git) is one of the commonly used logging framework for C++, and it would be good to have the logging appender for the framework using logging bridge API. More details:...
Upgrade otel-webserver-module CI to opentelemetry-cpp 1.15.0. If possible, please use semantic conventions from opentelemetry-cpp, instead of local constants such as: ``` const std::string kServiceName = "service.name"; ``` as found in...
Release opentelemetry-cpp-contrib 1.15.0, in sync with opentelemetry-cpp 1.15.0 Waiting for: * #430 * #432 * #433
Environment: openresty 1.25.3 opentelemetry-cpp-contrib version: v1.0.4 Refer to this document: https://opentelemetry.io/blog/2022/instrument-nginx/ I have the following configuration, after the configuration is complete when using openresty -t calibration it shows error unknown...
Some more resource attributes could be exported with the spans. Like request and response headers.
Most (all?) mod_opentelemetry logs use `NGX_LOG_ERR` severity (see e.g. https://github.com/open-telemetry/opentelemetry-cpp-contrib/blob/a02e0052e43934a9cffe23315750be03dc22dc3d/instrumentation/otel-webserver-module/src/nginx/ngx_http_opentelemetry_module.c#L671) This is not so nice, since those are expected messages and are not created because of errors, so it seems...
**Describe your environment** OpenTelemetry sdk: v1.8.1 Nginx: v1.21.6 Ingress-Nginx: v1.8.4 k8s: 1.24.6 **Steps to reproduce** - HIghload Nginx. - The collector's OpenTelemetry host is unavailable. **What is the expected behavior:**...
Please add aryanishan1001 in file README.md, in the approvers section.
**Situation A** NGINX 1.26.x or 1.25.x and **NO** OTEL cpp-contrib added. Requests made with curl, python httpclient are accepted. Requests made with dotnet 8.0 httpclient are acceepted. **Situation B** NGINX...
In [APIcast](https://github.com/3scale/apicast), the opentelemetry instrumentations is working for the default W3C propagator. When trying to switch to `b3` propagation type (i.e. `opentelemetry_propagate b3;`) propagation stops working, even though traces are...
