oliveromahony

hi I think this request is necessary and will help in categorization of OTel data in the case of this module. The issue I foresee is that the proposal quoted...

> Some general notes: > > * keep proto separate from generated bindings Where is this recommendation from? > * using full path , i.e. f5.nginx.agent.api.grpc.mpi.v1.common.MessageRequest for imports? I think...

> We don't have a naming convention for the package. I prefer the longer one since it shows where the source originated from https://protobuf.dev/programming-guides/style/#packages

hi @happydogggg Thanks for creating the issue. I ran the example server locally for me and got the following: ``` go run sdk/examples/server.go INFO[0000] http listening INFO[0000] gRPC listening ```...

Thanks for the issue @7wingfly. You can see how to get a NGINX config from the Management Server perspective in https://github.com/nginx/agent/blob/main/sdk/examples/server.go#L83 Right now there is no REST API on the...

hi @marcfielding1 thanks for your question! We have docs on securing the REST API: https://docs.nginx.com/nginx-agent/getting-started/#enable-the-rest-interface The configuration would look similar to this: ``` api: # Set API address to allow...

no problem @marcfielding1 If you configure the appropriate TLS certs you can hit the endpoint only using the client certificate. An example configuration of this would be using ``` make...

Note: the above is for illustration purposes only and is not recommended for production use

This is a feature request as we haven't implemented it just yet. We had it on our backlog to do

@dani3lsf @alexandear is there any updates on this? It is impacting fiber generation for my headers