kualico/nats-streaming-console

A web console for Nats Streaming Server

nats-streaming-console's Issues

Ability to show message, that not acknowledged yet

Or simply pending messages on channel)

is this project still maintained please?

Keep the state when a page is refreshed

I propose my contribution to keep the selected elements selected when the user refresh the page :

• in the /clients page : keep selected client and subscription
• in the /channels page : keep selected channel

What do you think ?

Unable to compile on Mac

Monitor gateway timeout - traefik ?

Hi,

I got it working via the IP but I tried to configure it via traefik and i get gateway timeout.

Anybody managed to get it working ?

version: "3.1"

services:
  nats-streaming:
    image: nats-streaming:latest
    restart: always
    command: ["--store", "file", "--dir", "./data", "-m", "8222"]
    volumes:
      - nats-streaming-volume:/data
    ports:
      - "4222:4222"
      - "6222:6222"
      - "8222:8222"

  nats-streaming-console:
    build:
      context: ./nats-streaming-console
      dockerfile: Dockerfile
    environment:
      - STAN_URL=nats://nats-streaming:4222
      - STAN_MONITOR_URL=http://nats-streaming:8222

    labels:
      - traefik.port=8282
      - traefik.frontend.rule=Host:monitor.mytestdomain.com
      - traefik.frontend.entryPoints=https,http

volumes:
  nats-streaming-volume:

networks:
  external:
    external: true

I know traefik is only an http proxy, and thats all that i am trying to do. Proxy the console web app.

Any ideas ?

I am at a loss

Thanks in advance

need a way to put this app on a /location/

is it doable to put this app on an nginx location ?
something like this
location /nats-streaming-console/ {
proxy_pass http://127.0.0.1:8282/;
...
....
}

Possible enhancements

I tried the app inside Kubernetes deployment and works quite nicely. Thanks for taking the effort to build this.

Here are a couple of possible enhancement requests I have. I believe this will help it to be used in production scenarios

• To only use the monitoring endpoint.
  Currently, as I noticed the console also takes the URL of the nats-streaming-server. It is also creating additional subscriptions. I see that it can be useful in certain cases. But for production scenarios, it would be good to make this feature optional.

• To have kubernetes deployment file (helm charts). I can contribute here.

• Adding more troubleshooting information for subscriptions (messages consumed, lag). I suppose such metrics can be derived.

How do I pass parameters to the application?

PS C:> docker run kuali/nats-streaming-console
{ options:
{ server: 'nats://localhost:4222',
monitor: 'http://localhost:8222',
cluster: 'test-cluster',
appName: 'nats-streaming-console' } }
Example app listening at http://:::8282

How do I change the cluster name etc.? (I am sure this is something I should know from a docker perspective.)

Update Docker Hub Image?

It seems that Docker Hub image is 6 months old.

Why not link Github with Docker Hub so that it's built automatically?

Ability to publish message

Would be cool to have ability to publish message to some channel

Channel message stuck on "Loading..."

I'm using nats-streaming with a skaffold local instance.
The ports 8222 and 4222 are forwarded to localhost.

When I go to /channels, I can see all my active channels but when I click on one of theme the right pannel is stuck on "Loading..."

Hi not work!

sudo npm install
npm WARN deprecated [email protected]: This version of react-dom/server contains a minor vulnerability. Please update react-dom to 16.2.1 or 16.4.2+. Learn more: https://fb.me/cve-2018-6341
npm WARN deprecated [email protected]: core-js@<2.6.8 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2.
npm WARN deprecated [email protected]: Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin
npm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated [email protected]: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated [email protected]: I wrote this module a very long time ago; you should use something else.
npm WARN deprecated [email protected]: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated [email protected]: Please migrate to Workbox: https://developers.google.com/web/tools/workbox/guides/migrations/migrate-from-sw
npm WARN deprecated [email protected]: Please migrate to Workbox: https://developers.google.com/web/tools/workbox/guides/migrations/migrate-from-sw
Killed.............] / fetchMetadata: sill mapToRegistry uri https://registry.npmjs.org/webpack-dev-middleware
[martin@myservice-pc nats-streaming-console]$
[martin@myservice-pc nats-streaming-console]$
[martin@myservice-pc nats-streaming-console]$ sudo npm run build-css

[email protected] build-css /home/martin/natsboard2/nats-streaming-console
node-sass-chokidar --include-path ./node_modules src/ -o src/

sh: node-sass-chokidar: command not found

npm ERR! Linux 3.10.0-957.12.2.el7.x86_64
npm ERR! argv "/usr/bin/node" "/bin/npm" "run" "build-css"
npm ERR! node v6.17.1
npm ERR! npm v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] build-css: node-sass-chokidar --include-path ./node_modules src/ -o src/
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] build-css script 'node-sass-chokidar --include-path ./node_modules src/ -o src/'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the nats-streaming-console package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-sass-chokidar --include-path ./node_modules src/ -o src/
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nats-streaming-console
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nats-streaming-console
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! Please include the following file with any support request:
npm ERR! /home/martin/natsboard2/nats-streaming-console/npm-debug.log
[martin@myservice-pc nats-streaming-console]$
[martin@myservice-pc nats-streaming-console]$ npm run build-css

[email protected] build-css /home/martin/natsboard2/nats-streaming-console
node-sass-chokidar --include-path ./node_modules src/ -o src/

sh: node-sass-chokidar: command not found

npm ERR! Linux 3.10.0-957.12.2.el7.x86_64
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "run" "build-css"
npm ERR! node v6.17.1
npm ERR! npm v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] build-css: node-sass-chokidar --include-path ./node_modules src/ -o src/
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] build-css script 'node-sass-chokidar --include-path ./node_modules src/ -o src/'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the nats-streaming-console package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-sass-chokidar --include-path ./node_modules src/ -o src/
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nats-streaming-console
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nats-streaming-console
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! Please include the following file with any support request:
npm ERR! /home/martin/natsboard2/nats-streaming-console/npm-debug.log
[martin@myservice-pc nats-streaming-console]$ sudo npm run build-css

[email protected] build-css /home/martin/natsboard2/nats-streaming-console
node-sass-chokidar --include-path ./node_modules src/ -o src/

sh: node-sass-chokidar: command not found

npm ERR! Linux 3.10.0-957.12.2.el7.x86_64
npm ERR! argv "/usr/bin/node" "/bin/npm" "run" "build-css"
npm ERR! node v6.17.1
npm ERR! npm v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] build-css: node-sass-chokidar --include-path ./node_modules src/ -o src/
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] build-css script 'node-sass-chokidar --include-path ./node_modules src/ -o src/'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the nats-streaming-console package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-sass-chokidar --include-path ./node_modules src/ -o src/
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nats-streaming-console
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nats-streaming-console
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! Please include the following file with any support request:
npm ERR! /home/martin/natsboard2/nats-streaming-console/npm-debug.log
[martin@myservice-pc nats-streaming-console]$
[martin@myservice-pc nats-streaming-console]$ sudo npm run build

[email protected] build /home/martin/natsboard2/nats-streaming-console
react-scripts build

sh: react-scripts: command not found

npm ERR! Linux 3.10.0-957.12.2.el7.x86_64
npm ERR! argv "/usr/bin/node" "/bin/npm" "run" "build"
npm ERR! node v6.17.1
npm ERR! npm v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] build: react-scripts build
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] build script 'react-scripts build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the nats-streaming-console package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! react-scripts build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs nats-streaming-console
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls nats-streaming-console
npm ERR! There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! Please include the following file with any support request:
npm ERR! /home/martin/natsboard2/nats-streaming-console/npm-debug.log
[martin@myservice-pc nats-streaming-console]$
[martin@myservice-pc nats-streaming-console]$ node server
module.js:478
throw err;
^

Error: Cannot find module 'express'
at Function.Module._resolveFilename (module.js:476:15)
at Function.Module._load (module.js:424:25)
at Module.require (module.js:504:17)
at require (internal/module.js:20:19)
at Object. (/home/martin/natsboard2/nats-streaming-console/server/index.js:2:17)
at Module._compile (module.js:577:32)
at Object.Module._extensions..js (module.js:586:10)
at Module.load (module.js:494:32)
at tryModuleLoad (module.js:453:12)
at Function.Module._load (module.js:445:3)
[martin@myservice-pc nats-streaming-console]$
[martin@myservice-pc nats-streaming-console]$ sudo node server
module.js:478
throw err;
^

Error: Cannot find module 'express'
at Function.Module._resolveFilename (module.js:476:15)
at Function.Module._load (module.js:424:25)
at Module.require (module.js:504:17)
at require (internal/module.js:20:19)
at Object. (/home/martin/natsboard2/nats-streaming-console/server/index.js:2:17)
at Module._compile (module.js:577:32)
at Object.Module._extensions..js (module.js:586:10)
at Module.load (module.js:494:32)
at tryModuleLoad (module.js:453:12)
at Function.Module._load (module.js:445:3)
[martin@myservice-pc nats-streaming-console]$

not showing in browser. Getting “Not here”

everything builds but in the browser i get “Not here” shown.

Nats Streaming is running using:

nats-streaming-server -store file -dir data/store -m 8222

Standard Nats Monitoring at localhost://8222 shows the GUI, so standard monitoring is working.

nats-streaming-console is running using:

make dash-run
cd /Users/apple/workspace/go/src/github.com/KualiCo/nats-streaming-console && node server
{
  options: {
    server: 'nats://localhost:4222',
    monitor: 'http://localhost:8222',
    cluster: 'test-cluster',
    appName: 'nats-streaming-console'
  }
}
Example app listening at http://:::8282

Building nats-streaming-console with:

LIB_NATSDASH=github.com/KualiCo/nats-streaming-console
LIB_NATSDASH_FSPATH=$(GOPATH)/src/$(LIB_NATSDASH)

### nats streaming console dash
dash-dep:
	go get $(LIB_NATSDASH)
dash-dep-clean:
	rm -rf $(LIB_NATSDASH_FSPATH)
dash-code:
	code $(LIB_NATSDASH_FSPATH)
dash-build:
	cd $(LIB_NATSDASH_FSPATH) && npm install
	cd $(LIB_NATSDASH_FSPATH) && npm build-css 
	cd $(LIB_NATSDASH_FSPATH) && npm build
dash-run:
	cd $(LIB_NATSDASH_FSPATH) && node server
	open http://0.0.0.0:8282

`npm run build` fails

Some .js files imports .css files, but actual suffixes are .scss.

% git clone https://github.com/KualiCo/nats-streaming-console.git
% cd nats-streaming-console
% npm install
...
% npm run build

> [email protected] build /home/hidai/nats/nats-streaming-console
> react-scripts build

Creating an optimized production build...
Failed to compile.

Module not found: Error: Can't resolve './index.css' in '/home/hidai/nats/nats-streaming-console/src'


npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: `react-scripts build`
npm ERR! Exit status 1
npm ERR!-
npm ERR! Failed at the [email protected] build script.

Error "Not here."

Try go to http://localhost:8282/ -> redirect -> http://localhost:8282/server
Response body: Not here.

WTF?