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
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.
The text was updated successfully, but these errors were encountered:
abbi-gaurav
changed the title
Only consuming the monitoring API
Possible enhancements
Oct 12, 2018
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.
The text was updated successfully, but these errors were encountered: