Skip to content

Conversation

asmit27rai
Copy link

Kubestellar Monitoring Plugin Added

Signed-off-by: asmit27rai <raiasmit10@gmail.com>
Signed-off-by: asmit27rai <raiasmit10@gmail.com>
@dumb0002
Copy link

@gaurab-khanal, is this PR in good shape to be merged?

@gaurab-khanal
Copy link
Member

@gaurab-khanal, is this PR in good shape to be merged?

@dumb0002 Not yet, once we fix the port conflict issue regarding UI grafana server and kubestellar core monitoring then only we can merge

@dumb0002
Copy link

@gaurab-khanal, is this PR in good shape to be merged?

@dumb0002 Not yet, once we fix the port conflict issue regarding UI grafana server and kubestellar core monitoring then only we can merge

@gaurab-khanal, do we have an issue open to keep track of the port conflict problem?

@gaurab-khanal
Copy link
Member

@gaurab-khanal, is this PR in good shape to be merged?

@dumb0002 Not yet, once we fix the port conflict issue regarding UI grafana server and kubestellar core monitoring then only we can merge

@gaurab-khanal, do we have an issue open to keep track of the port conflict problem?

@dumb0002 We are discussing it in slack channel.

@clubanderson
Copy link
Contributor

@gaurab-khanal what is the latest on this - would like to get this merged soon

@gaurab-khanal
Copy link
Member

@clubanderson PR looks good and can be merged. Only thing that is holding this PR is the port related issue that we have discussed in slack.

@clubanderson
Copy link
Contributor

@MAVRICK-1 @btwshivam can you change the default port for prometheus and grafana included with our UI (manual, docker install, etc) so that it does not interfere with someone installing these 2 items in their kube environment on the same cluster? If so, then this will unblock this PR

@MAVRICK-1
Copy link
Member

@asmit27rai why using separate port you default grafana port in the ui and add the chart into it . I think I already told you about this

@clubanderson
Copy link
Contributor

no, @asmit27rai is to use the standard port. Our UI needs to use a different, non-standard port so we do not interfere with routine monitoring of anything else

@asmit27rai
Copy link
Author

@MAVRICK-1 The issue arises due to a port conflict with Grafana. Both the UI and the Monitoring Tool are configured to use the same port (3000) for Grafana. When both services run simultaneously—particularly when the UI attempts to display monitoring graphs—this shared port causes conflicts, resulting in runtime issues.

@clubanderson
Copy link
Contributor

@MAVRICK-1 do you have the time to and are you able to make the change for our grafana and Prometheus packages included with our UI or do we need to create a help wanted to have someone else do it?

@MAVRICK-1
Copy link
Member

@clubanderson i have to understand how they are fetching the data? . @asmit27rai in the pr there nothing in backend go code it's just responding version, how it is fetching the metrics?

@clubanderson
Copy link
Contributor

I didn't ask that question. When someone adds Prometheus and grafana after our project is installed it fails. People do this all the time on kubernetes. They do this to own and control monitoring of whatever they like. I need someone to change our default ports in our packaged versions.

@MAVRICK-1
Copy link
Member

Okay I will do that by today

@clubanderson
Copy link
Contributor

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants