Is your feature request related to a problem? Please describe.
In many (smaller-to-medium) deployment scenarios, we make use of the embedded NATS server that is running within the opencloud binary.
The NATS server, including the embedded one, is able to provide an HTTP endpoint for monitoring (e.g. using nats-top as well as for collecting Prometheus metrics using prometheus-nats-exporter.
Currently, that endpoint is not enabled and there are no configuration options to do so.
It might be helpful to debug where connections and load are coming from.
Describe the solution you'd like
Add configuration options for the embedded NATS server in the backend in order to
- enable the monitoring endpoint or not (disabled by default)
- on which address to bind to (localhost by default)
- on which port to bind to (8222 is the default for that NATS monitoring endpoint)
- whether to use HTTPS or HTTP
Describe alternatives you've considered
The only alternative without this change is to operate a standalone NATS server process/container/pod that is then used by the opencloud binaries instead of the embedded one.
Is your feature request related to a problem? Please describe.
In many (smaller-to-medium) deployment scenarios, we make use of the embedded NATS server that is running within the
opencloudbinary.The NATS server, including the embedded one, is able to provide an HTTP endpoint for monitoring (e.g. using
nats-topas well as for collecting Prometheus metrics usingprometheus-nats-exporter.Currently, that endpoint is not enabled and there are no configuration options to do so.
It might be helpful to debug where connections and load are coming from.
Describe the solution you'd like
Add configuration options for the embedded NATS server in the backend in order to
Describe alternatives you've considered
The only alternative without this change is to operate a standalone NATS server process/container/pod that is then used by the
opencloudbinaries instead of the embedded one.