Colin Sullivan

We feel this will be resolved by #2815; additional testing will determine if that PR covers everything we need. @c16a , thank you so much for the offer to help...

With regards to the buffered writer on reconnect, the buffer could be trimmed to discard a partial message before sending the data to the server. Thoughts?

Would this be good for the NKIT APIs vs core NATS?

@Takashi-kun , Thank you for using NATS. Can you describe in more detail about you are asking for? RTT between routes, or between a client and server? We have a...

You could try exposing the port, e.g. ``` expose: - "7777" ``` https://docs.docker.com/compose/compose-file/#expose

@jebbench , we discussed this internally today and will move forward with some design in this area. We really appreciate your suggestion!

I think this is a good idea. It'll require more maintenance as new metrics from servers are exposed, but will be the correct way to do this.

@laugimethods , great suggestion; I feel both max and rate are valuable for different reasons. Throughput could certainly be added as another row in the dashboard.

@robertmircea , yes this can happen. If the ack from the client was sent but the NATS streaming server was shutdown/crashed before processing the ack, the original message may be...

@robertmircea , this is very specific to your use case and we'd have to learn more about it. What is your subscriber doing - does it save data someplace? One...