Open saravanan30erd opened 4 years ago
Hello @saravanan30erd ,
I still don't get what's the purpose of this implementation. Maybe we're using Monit in different ways, so let me add a couple of screenshots on my current setup:
Current master
branch:
This pull request:
In this case, as a user watching the dashboard, I have to click more times to see what's wrong, and my services are categorized in a non-intuitive way.
I have the Monit service installed on each server I want to monitor (the Monit dashboard/MMonit polls all of them every time), and I believe your approach is to have one single Monit server monitoring all your servers.
Can you please clarify?
@adriaaah Yes, I have one centralized monit server monitoring all the servers/services.
To be honest I don't know how to proceed here. I was considering adding a flag or a config parameter to let the user choose the view, but I think it's pretty much effort considering the number of files involved. Any suggestion is more than welcome.
@adriaaah currently all the services are listing under single server(button). But usually the services are categorized into many layers such as production, staging, ssl check, http check, database server check, tcp port check. so we can categorize the services based on this functionality type and show the services in sub-categories instead of showing all the services in single button, because it requires to scroll the page more and more if the services list is more.
Dependency is, when you creating the service in monit backend we need to follow the format like this,