You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a --details argument to collect detailed information on the server endpoints in audit. This would model the arguments in the current server request commands when the --details --server-endpoints arguments are passed.
nats server request connections --subscriptions
nats server request gateways --accounts --subscriptions
nats server request jetstream-health --details
nats server request jetstream --all --config
nats server request leafnodes --subscriptions
nats server request routes --subscriptions
nats server request subscriptions --detail
Use case
This information can often be useful in debugging. Making it opt-in will help reduce the size of the output file and allow the user to opt into sharing that level of data.
Contribution
No response
The text was updated successfully, but these errors were encountered:
Always on with an opt-out would be great. The opt-out is mainly when we don't need the data and there could be sensitive strings in the subject or stream/consumer descriptions. That is unlikely, but it is a nice to have option in those cases.
Proposed change
Add a
--details
argument to collect detailed information on the server endpoints in audit. This would model the arguments in the current server request commands when the--details --server-endpoints
arguments are passed.nats server request connections --subscriptions
nats server request gateways --accounts --subscriptions
nats server request jetstream-health --details
nats server request jetstream --all --config
nats server request leafnodes --subscriptions
nats server request routes --subscriptions
nats server request subscriptions --detail
Use case
This information can often be useful in debugging. Making it opt-in will help reduce the size of the output file and allow the user to opt into sharing that level of data.
Contribution
No response
The text was updated successfully, but these errors were encountered: