Maybe the command in sql_store.md should be update about nats.docs

[kozlovic]

In my situation, monitoring port was not exposed until I added -m. The behavior seems to be different from what you described.

No, like you wrote, you need -m 8222 to have the streaming server start the monitoring http server on that port. So this command is a way to do it:

docker run -p 4222:4222 -p 8222:8222 nats-streaming -m 8222 ...

My original goal was to let nats save all the messages so that I can check them manually if something goes wrong.
Can this purpose be achieved without -SDV?

Yes. The option -SDV causes the server to print debug/trace information. It is usually not recommended to run this in production because it affects performance.

by using SELECT encode(data, 'ESCAPE') FROM "messages".
There are some mysterious things on both ends. What are the steps to get the message manually in postgres database?

This is expected. NATS Streaming saves the message as a blob. The content is actually a protobuf serialized pb.MsgProto (see: https://github.com/nats-io/stan.go/blob/master/pb/protocol.proto#L47 and https://github.com/nats-io/stan.go/blob/master/pb/protocol.pb.go#L105).

[gcolliso]

@kozlovic / @wallyqs - could you review this issue and let me know what changes, if any, need to happen? Thx

[kozlovic]

@AHBICJ You are right. The image name should be nats-streaming, not nats-streaming-local. The original exports the monitoring port 8222 but does not start it with -m 8222 after image name.
I would even remove the -SDV from this command because this adds debug and traces and can be verbose and affect performance. It could be mentioned that it could be added for debug if needed.

@AHBICJ Would you want to submit a PR with the changes you are proposing? If you can't/don't want, no worries, we can do it for you.

[AHBICJ]

@kozlovic I want to clarify one of my problems.
In my situation, monitoring port was not exposed until I added -m. The behavior seems to be different from what you described.

My original goal was to let nats save all the messages so that I can check them manually if something goes wrong.
Can this purpose be achieved without -SDV?

I hope you can answer my other question not related to this issue.
I get something like

����foo" Hello World(\300\266\205\271\304\333\267\244�

by using SELECT encode(data, 'ESCAPE') FROM "messages".
There are some mysterious things on both ends. What are the steps to get the message manually in postgres database?

I am not very familiar with nats yet, and will not submit a PR, so please @gcolliso update this file.

Last point, thank you for your reply.

[AHBICJ]

@kozlovic Thank you very much for your efforts and answers

[kozlovic]

@AHBICJ Just to confirm: are you planning on submitting a PR for the changes in the doc or should we do it instead?

[AHBICJ]

@kozlovic you do instead please, thanks!

[kozlovic]

@AHBICJ Please check #176 to see if it addresses your concerns. The password in the sql_source was also wrong..

[AHBICJ]

@kozlovic very well, thx again