p-pautov

Looks like, this is due to [CMP0126](https://cmake.org/cmake/help/latest/policy/CMP0126.html). Using `set(gRPC_RE2_PROVIDER package CACHE INTERNAL "")` in super project should avoid the issue.

This is reasonable request, but Nginx doesn't provide clear "hook" points around upstream calls in all cases. The only option I can think of so far is to introduce new...

@bmerigan, subrequests tracing might deserve its own issue. Also, can you share config example so it's clearer what those subrequests are used for (e.g. authentication)?

We are going to implement TLS export, but I'm not sure about 'insecure_skip_verify'. If you need such option, perhaps, you don't really need TLS. As a workaround for now you...

I think, we can add generic `otel_resource` block, which would allow setting any resource level attributes, e.g. ``` otel_resource { "deployment.environment" "prod"; "service.node.name" "mysvc"; "service.version" "1.0"; } ```

I don't think, you have to have identical configs on each instance. Say, you can use instance specific file and include it into synced config. Another option is to use...

If you are building Nginx from source, then you should have most of these packages already installed. CentOS equivalents of last two seem to be "c-ares-devel" and "re2-devel" and if...

I believe, cmake looks for `OPENSSL_ROOT_DIR` in environment variables as well. So does setting it as an environment variable directly works for you?

There is #32 to support custom resource attributes via config, but supporting environment variables like OTEL_RESOURCE_ATTRIBUTES and OTEL_SERVICE_NAME makes sense as well.

Can you provide minimal and complete config example to reproduce the issue? I'd guess, that "/private_api" location disables tracing.